47
Selfhosting GitLab? (sh.itjust.works)
submitted 1 month ago* (last edited 1 month 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
[-] jimmy90@lemmy.world 3 points 1 month ago

do the front end in Leptos and host it on ForgeJo

[-] shaserlark@sh.itjust.works 1 points 1 month ago* (last edited 1 month ago)

I'm intrigued! But how does it compare to React which is pretty straight forward? I'm not a frontend dev so what's really great about React is that it works super well with LLMs.

[-] jimmy90@lemmy.world 2 points 1 month ago

Leptos is very React-like but it's Rust so it will be Rusty sometimes. you mentioned you've done the back end in Rust anyway.

with LLMs do you mean code suggestions like code-pilot or actually integrating with an LLM api?

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

Selfhosted

40716 readers
339 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