this post was submitted on 23 Nov 2024
47 points (98.0% liked)

Selfhosted

40696 readers
309 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
47
Selfhosting GitLab? (sh.itjust.works)
submitted 4 weeks ago* (last edited 3 weeks ago) by shaserlark@sh.itjust.works to c/selfhosted@lemmy.world
 

I’ve started building a small decentralized, non commercial app with a Rust backend + Node.js frontend running on k8s. I would have my own dedicated server for this. Just mentioning the setup because it might grow and for git there seem to be only GitHub and GitLab around and I prefer GitLab.

I care a lot about security and was wondering if it makes sense to self-host GitLab. I‘m not afraid of doing it, but after setup it shouldn’t take more than 1-2 hours per week for me to maintain it in the long run and I’m wondering if that’s realistic.

Would love to hear about the experience of people who did what I’m planning to do.

EDIT: Thanks for all the answers, trying my best to reply. I want CI/CD, container registry and secrets management that's what I was hoping to get out of GitLab.

you are viewing a single comment's thread
view the rest of the comments
[–] WalnutLum@lemmy.ml 2 points 4 weeks ago (1 children)

Yea a surprisingly small number of people don't know a git remote can literally be any folder outside of your tree, over almost any kind of connection.

I thought about doing a forge but realized that if I was the only one working on this stuff then I could do the same thing by setting my remote to a folder on my NAS.

[–] interurbain1er@sh.itjust.works 1 points 4 weeks ago

Yup, for a solo project that you don't want to share I would even argue that a forge is close to pointless.

Any ssh remote will work as a backup, you can run the ci/cd task on your own computer just fine (very likely faster even), you obviously don't need to send PR and request code review to yourself and if a TODO.md isn't enough to keep track of tasks there's a billions lightweight task/note tracker.

I use github because I'm a lazy and it works fine as a backup but I don't need 99% of the features for my pet projects.