Replying to an earlier post

You don’t see the deal breaker because your requirements are clearly low enough that open-core software works for your use case. Your experience is not universal. Your inexperience is leading you to believe you’re more knowledgeable than you really are. I don’t need to explain myself to someone that engages in bad faith arguments.

Let me guess, you chose Gitlab because you’re a DHH fanboy?

Replying to an earlier post

Nobody asked you? Why do we care what you think?

Nobody asked you in particular, either, but here we are like 3-4 replies deep anyway. Even if we had, you’ve refused to answer so you can act like a smug cunt instead, so you’d apparently be useless at it anyway.

Sounds to me like you’re insecure and looking for a free handout instead of being able to come up with a coherent reason for why you’re owed something you’ve not earned.

My guy, then just shut the fuck up. You don’t have to use it as an opportunity to grandstand and fellate yourself for being so smart to get it. You could just say nothing if you don’t want to actually contribute. Honestly, you’ve been worse than useless here.

Replying to @⁨AHemlocksLie@lemmy.zip⁩

You’re spending an awful lot of time telling me I don’t get to reply to comments off my own thread. Maybe stop and realize that my original comment didn’t need any replies and y’all are the ones wasting your time and energy arguing downthread instead of getting smart enough to go start your own thread if you want to express yourself.

It’s 2026, not 1996. Its time to grow up and learn how threaded conversations work. They aren’t new. It’s awful weird that you’re struggling so much with the concept.

But sure. Keep screeching “STFU” like a child. I’m sure that somehow, somewhere, someone on the internet might actually listen to you. But that someone is not me. I don’t listen to the demands of children.

Replying to @⁨wakko@lemmy.world⁩

You’re getting blasted for some reason lol

To add some context, GitHub’s primary strength is integrating different services. GitLab’s primary strength is being “the one thing” that you use. It really depends on your business which one makes most strategic sense. For small to medium, GitLab is great. Even large it can work amazingly.

However, I’ll put my anecdotal two cents in and say that GitHub comes out ahead for very large enterprises, or if you do collaborative, or Business 2 Business stuff, just because of it’s integrations. Integrations are king once you get to scale. If you’re using GitLab + anything else, it’s friction for each additional tool you use, rather than a force multiplier. At a certain point it restricts you.

Replying to @⁨dhruv3006@lemmy.world⁩

lemmy.mlSelf Hosted - Self-hosting your services. - LemmyA 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 - No harassment - crossposts from c/Open Source & c/docker & related may be allowed, depending on context - Video Promoting is allowed if is within the topic. - No spamming. - Stay friendly. - Follow the lemmy.ml [http://lemmy.ml] instance rules. - Tag your post. (Read under) # Important - Lemmy doesn’t have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged! # Cross-posting - !everything_git@lemmy.ml [/c/everything_git@lemmy.ml] [https://lemmy.ml/c/everything_git] is allowed! - !docker@lemmy.ml [/c/docker@lemmy.ml] [https://lemmy.ml/c/docker] is allowed! - !portainer@lemmy.ml [/c/portainer@lemmy.ml] [https://lemmy.ml/c/portainer] is allowed! - !fediverse@lemmy.ml [/c/fediverse@lemmy.ml] [https://lemmy.ml/c/fediverse] is allowed if

Replying to an earlier post

Hmm not natively but I think you could hack something together using git plumbing, perhaps just some hooks. I would still advise against adding secrets to version control even if it stays completely local though, it’s still “bad hygiene” and something you should try to avoid. You don’t need to go with a full-fledged secret management solution, just keep your secrets in .envs or similar external files and use a password manager to store your live keys. Of course it all depends on the specific context, if it’s something bound to loopback I’m not going to stop you from running admin:admin and committing that to your personal docker-compose stash, but if it’s protecting something you care about don’t put it in git.