You could host on Gitea and mirror to GitHub. Obviously, users may be less inclined to sign up to your Gitea instance, but I hope people being unwilling to register becomes less of an issue once Forgejo (Gitea fork) implements forge federation.
Programming, cybersecurity, privacy, self-hosting, and some other stuff.
You could host on Gitea and mirror to GitHub. Obviously, users may be less inclined to sign up to your Gitea instance, but I hope people being unwilling to register becomes less of an issue once Forgejo (Gitea fork) implements forge federation.
I hope this changes (even if a little bit) once Forgejo (FLOSS Gitea fork) adds forge federation.
when you copy/paste a file on your computer it’s much faster than copying the file
I think you meant ‘when you cut/paste a file’?
This is a pretty good option, though I also think something like what aseprite has done is pretty good too (compile it yourself for free, or pay for a precompiled binary available through e.g. Steam) - from what I can tell this setup is fairly profitable.
Well, I’m not sure how many lines of C rm is written in but I think that rm being only around 4kb (iirc) is something to consider.
But still, storage probably matters least in this day and age. Oh, and…
something I used to completely nuke my home server
If I’m reading this right, then I hope you had backups ready :)
Nah, no way. :)
This probably isn’t the answer you’re looking for, but vpr
being memory-safe isn’t a benefit that it has over rm
, since rm
apparently doesn’t allocate any memory (as @radiant_bloom@lemm.ee wrote).
the first thing you mentioned as a benefit was memory safety.
Looks like I worded my project description poorly. As I wrote in another comment, I meant that this alternative is memory-safe (being written in safe Rust), but not that rm
isn’t.
edit: I’ve updated the post’s title to clear things up
I guess vpr -x
would be memory-safe that way then. ;)
I don’t know whether rm
is memory-safe or not, but vpr
is. By ‘memory-safe alternative’ I meant that this alternative is memory-safe, but not that rm
isn’t.
Happy to hear that you like it :)
Go for it! It’s pretty simple but does help teach a few things.
If you want to keep everything inside a singular Nix configuration while still using Docker, you can check out the NixOS option
virtualisation.oci-containers
- essentially, a declarative way of managing docker/podman containers (similar to docker-compose) but with Nix.