For me it’s probably the way I self-host overleaf, a online LaTeX editor. The community version has a docker image that’s horribly maintained (because they want to sell enterprise, I reckon), and instead relies on a horrendous amalgamation of setup scripts that wrap docker compose.

What I have is a Dockerfile that pulls the image, manually installs a second version of TeX with the right dependencies, unlinks the old one and links the second one. Then for the database, it uses Mongo replsets, which be to be manually initialized. So I wrote a health check for the container that checks if the repl set is initialized, and if that fails the health check initializes it.

It’s horrendous, it’s disgusting, and it’s an all-in-one compose file to get overleaf running. Good enough.

You could try emailing the FSF and explaining your situation. They constantly get into legal battles over licencing and care a whole lot about open source. Their opinion is certainly a lot more expert than what any of us can produce :D

That is probably something you should ask a lawyer for, not strangers on the Internet. But I think if you make the case that you already have a lot of the groundwork for the project published under GPL, you can massively reduce effort by using that, but that’ll mean the final project will be GPL licensed as well, most people would agree that’s a reasonable trade off. Just make sure it’s written somewhere, so they can’t pull a fast one on you

NixOS for my homelab that I like to tinker with, Debian as Docker host for the server people actually rely on

C to A adapters are sick and illegal

I still have some

Amazing shitpost

Preventing unwanted state

If you install and then uninstall something, it will almost certainly leave logs, configurations and other garbage in places you don’t expect. Next time you want to use it, it isn’t the clean install you expected

🅱️rogramming language

I’d rather have a 16kb/s seeder than a dead torrent

Under the shower for me

username… checks out?

I’ve really been enjoying Helix, which took a lot of inspiration (including key binds, mostly) from Kakoune. It’s just missing a plugin system to be perfect, but built in LSP support is soo nice

uBlock is licensed under the GPL-3, I can absolutely say the same

Let’s just hope they don’t blow any whistles before launch, or it might just catastrophically malfunction

The post was edited

Ah, thanks for the clarification ^-

I don’t use VSCode(ium) myself, I’m usually quite content with Helix + LSPs, and if ever need a full IDE I usually go with the Jetbrain products

I think you’re mixing up Visual Studio and Visual Studio Code. Visual Studio is a massively bloated IDE mostly used for .NET development, but supports other things too. It’s proprietary, massive, slow and a pain to work with, and doesn’t run on Linux afaik

Visual Studio Code, on the other hand, is an Electron app and therefore runs almost everywhere, and is (partly or totally, I’m not sure) open source. Nothing wrong with coding in VS Code, it’s a decent IDE

VS, not VS Code

Why anyone outside the Microsoft ecosystem would want to use Visual Studio though, idk

helix!

This feels like implementing a certificate authority system for individual users I wonder if it is feasible to use of a web of trust that is less cumbersome and more resilient than the original GnuPG WoT, that could do the same thing. Instead of hierarchical introductions you have trusted users vouch for you not being a bot (one could even think about extending this to general rule abidance, turning it into a full on reputation system). It would feel pretty bad to loose an account, just because whoever invited you later also invited a bunch of bots/untrustworthy users