floquant
joined 2 years ago
Psh, we all know life is toroidal
DNS is like spiders. The visceral fear is justified, but if you can get over it you can learn interesting things and have fun
Manual intervention announcements happen far from "often" though, tinkering with your system is a different thing
If it can be waived, then it's a temporary privilege, not a right
Chip companies are cutting off consumers on purpose. They lost your $100 business and gained $1000 sales on the same products
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.
Ah, it's me who's certain to be right and is avoiding discussion by being elitist, sure.
Bye, enjoy refreshing GitHub for hours
That's a lot of words over two comments to avoid answering a simple question
No, I have just migrated my company to self-hosted GL and found a better experience with literally no downsides.
I think it is a fair question, because I really don't see what could be the deal-breaker. Is it copilot, or the terrible GitHub actions?
Right after they announced they're doubling the required watch time to turn on monetisation, it's clear what they want - more volume, less quality. Slop, slop, slop.
view more: next ›