KomuSolutions/igot99issues
3
0
Issues 15 Projects 1 Wiki

Setup GitLab #60

New Issue
Open
opened 2024-12-11 11:13:50 +01:00 by lukas · 8 comments
lukas commented 2024-12-11 11:13:50 +01:00
Owner
Copy Link

Host a GitLab instance, e.g. lab.libre.moe

Opinions on DNS names welcome. (or generally on the setup of this instance)

Loosely depends on #58 for appropriate secondary DNS-names for the registry and such.

For now Gitea (git.libre.moe) and Gitlab will co-exist.

Host a GitLab instance, e.g. `lab.libre.moe` Opinions on DNS names welcome. (or generally on the setup of this instance) Loosely depends on #58 for appropriate secondary DNS-names for the registry and such. For now Gitea (`git.libre.moe`) and Gitlab will co-exist.
lukas added the
Priority
Medium
Domain
libre.moe
 labels 2024-12-11 11:13:50 +01:00
leon was assigned by lukas 2024-12-11 11:13:50 +01:00
lukas added this to the Issue Board project 2024-12-11 11:13:50 +01:00
lukas self-assigned this 2024-12-11 11:13:58 +01:00
lukas commented 2024-12-16 19:40:52 +01:00
Author
Owner
Copy Link

Dev instance looking good, I decided against LDAP as GitLab works very well with my existing OIDC system and to avoid unnecessary complexity. Will also introduce GitHub auth to allow external users to easily collaborate on Git.

Dev instance looking good, I decided against LDAP as GitLab works very well with my existing OIDC system and to avoid unnecessary complexity. Will also introduce GitHub auth to allow external users to easily collaborate on Git.
lukas commented 2024-12-16 20:11:16 +01:00
Author
Owner
Copy Link

Our deployment will use approximately 2-2.5 GiB memory on average, therefore 3 GiB should be reserved to run this instance.

With the current usage of ireul, which will be the target for this deployment, we need to scale this instance up to accommodate this requirement.

Our deployment will use approximately 2-2.5 GiB memory on average, therefore 3 GiB should be reserved to run this instance. With the current usage of `ireul`, which will be the target for this deployment, we need to scale this instance up to accommodate this requirement.
lukas added the
Status
Planned
 label 2024-12-17 12:22:20 +01:00
lukas commented 2024-12-23 14:09:35 +01:00
Author
Owner
Copy Link

I am currently thinking about using to use #62 to free up more RAM on ireul. In conjunction with a more aggressive GitLab configuration, it can probably be deployed without needing a server upgrade.

I am currently thinking about using to use #62 to free up more RAM on `ireul`. In conjunction with a more aggressive GitLab configuration, it can probably be deployed without needing a server upgrade.
lukas changed title from Gitlab to Setup GitLab 2024-12-23 14:10:03 +01:00
lukas commented 2024-12-23 14:13:25 +01:00
Author
Owner
Copy Link

Note to self: https://blog.palark.com/gitea-to-gitlab-migration/

Note to self: https://blog.palark.com/gitea-to-gitlab-migration/
lukas commented 2024-12-31 12:12:35 +01:00
Author
Owner
Copy Link

I'll try to host GitLab wird a hard limit of 3GB memory and set up a swapfile to be able to safely overprovision (my VM only has 3.41GB useable with 800MB minimum used currently)

I'll try to host GitLab wird a hard limit of 3GB memory and set up a swapfile to be able to safely overprovision (my VM only has 3.41GB useable with 800MB minimum used currently)
lukas commented 2024-12-31 14:05:38 +01:00
Author
Owner
Copy Link

Note on the matter: It appears that even runners support S3 as a backend for the cache, meaning our runners can cache straight to Hetzner S3. Furthermore, it appears as if we could setup autoscaling our runners with Hetzner directly: https://www.marc-willmann.de/gitlab-runner-autoscale-in-der-hetzner-cloud.

Note on the matter: It appears that even runners support S3 as a backend for the cache, meaning our runners can cache straight to Hetzner S3. Furthermore, it appears as if we could setup autoscaling our runners with Hetzner directly: https://www.marc-willmann.de/gitlab-runner-autoscale-in-der-hetzner-cloud.
lukas commented 2024-12-31 15:56:26 +01:00
Author
Owner
Copy Link

Gitlab instance is now up and ready for initial testing.
https://lab.libre.moe

Please report any problems in this issue for now.

Gitlab instance is now up and ready for initial testing. https://lab.libre.moe Please report any problems in this issue for now.
lukas commented 2025-01-01 16:47:37 +01:00
Author
Owner
Copy Link

Road to prod

  • SSH cloning
  • Container registry with dedicated endpoint
  • Fine tune Emails
  • Integrate to backup scripts
  • Auto cleanup logs
  • 24/7 runner
  • Draft: autoscaling runners
  • Test S3 backend with LFS
  • Test S3 backend with Artifacts
  • Verify S3 virtual path setup
### Road to prod - [x] SSH cloning - [ ] Container registry with dedicated endpoint - [ ] Fine tune Emails - [ ] Integrate to backup scripts - [ ] Auto cleanup logs - [ ] 24/7 runner - [ ] Draft: autoscaling runners - [x] Test S3 backend with LFS - [ ] Test S3 backend with Artifacts - [ ] Verify S3 virtual path setup
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Breaking

Breaking change that won't be backward compatible

  
Domain
komu.boo

  
Domain
langrock.info

  
Domain
libre.moe

  
Involves
Documentation
Issue invovles changing the documentation

  
Involves
Security
This is security issue

  
Involves
Testing
Issue or pull request related to testing

  
Kind
Bug
Something is not working

  
Kind
Enhancement
Improve existing functionality

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Service
Element

  
Service
Gitea

  
Service
Matrix

  
Service
Nextcloud

  
Service
Seafile

  
Service
Szuru|Kirei

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Duplicate
This issue or pull request already exists

  
Status
Invalid
Invalid issue

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Status
Planned
Issue has been confirmed and is planned to be resolved

  
Status
Won't Fix
This issue won't be fixed

No Label
Breaking
Domain
komu.boo
Domain
langrock.info
Domain
libre.moe
Involves
Documentation
Involves
Security
Involves
Testing
Kind
Bug
Kind
Enhancement
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Service
Element
Service
Gitea
Service
Matrix
Service
Nextcloud
Service
Seafile
Service
Szuru|Kirei
Status
Abandoned
Status
Blocked
Status
Duplicate
Status
Invalid
Status
Need More Info
Status
Planned
Status
Won't Fix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Issue Board
Assignees
Clear assignees
No Assignees
leon
lukas
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: KomuSolutions/igot99issues#60
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?