Yeah I agree. Although recently I’ve become partial to toml… In the end I’ll use what’s common in the ecosystem I’m developing in

Nothing too major about how it’s usually used, but the yaml spec does allow arbitrary code execution when parsing a file and relies on the parser to have that feature disabled: https://en.m.wikipedia.org/wiki/YAML#Security

That’s why for python, yaml.save_load() is a thing. That’s fine for your local config files and may even be a feature for you, but it shouldn’t be used to exchange information between services.

Don’t rely on VPNs as your (only) security, if you are at actual risk from your online activities. For piracy, it does not matter. Pick one you like

Nice

ngl, good job

but

“lol”, said the scorpion. “lmao”

of course they’re not a drop-in replacement, as the cli is getting a major redesign, but as per your source

nix shell and nix develop are still experimental, so nix-shell is sticking around despite doing the same thing

it seems like they are made to fulfill the same purpose

Interesting, didn’t know the history of the command. But that post confirms my understanding, that nix shell/develop are the new replacements for nix-shell, with nix shell for temporary package installs and nix develop for debugging and developing

Source on the second statement? My understanding was that nix-shell is legacy for systems without flakes and nix-command enabled, and are being replaced by nix shell/run/develop

Careful, there’s three different terms in the mix here:

NixOS: an entire operating system, you don’t need this.

nix: the nix package manager. This is what you’ll need to install. look for single user install in the instructions.

home-manager: a module for nix. It’s aim is to allow declarative configuration of a users’ home configuration (and allow easier per-user install of packages on a global nix install).

If you want to go down the nix route, which I would recommend if you enjoy tinkering and having fine control over your system, you should start with installing nix. With that, you can already setup a shell that has the newest version of python available.

Going beyond that, I can link you some more resources, if you want c:

Forgejo is a free/open source code hosting site like GitHub or Gitlab. It’s a fork of Gitea, over concerns with management and commercialization. You might know it from Codeberg, which is one of the largest managed instances, but it’s really easy to host your own.

I’d assume that’s already a bigger problem for satellites in geostationary orbit then?

“good news honey, they heard your complaint and renamed it”

For reproducibility, nothing really beats NixOS. That’s not really what you’re asking for, as that would not involve Clonezilla.

If you’re frequently switching hardware, and want to have everything up and running, configured to your liking, in minutes, you’re gonna have fun with NixOS in the long term. But I’m not gonna sugarcoat it, it has a steep learning curve and does require you to enjoy some tinkering. Worth it, imo

Otherwise, just pick a distro that you enjoy and create a separate home partition, when it’s time to switch you do a fresh install and clone only the home partition. That’ll get you 90% of the way to have your old setup on the new device

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

Amazing removedpost