4 ms·
I’ve been moving into a self-hosted direction for a lot of my stuff as a lot of it really wasn’t being used by anyone but myself anyhow. My latest two projects
by toastal 3y ago
I’ve been moving into a self-hosted direction for a lot of my stuff as a lot of it really wasn’t being used by anyone but myself anyhow. My latest two projects are darcs on my home server using just SSH+Nginx for HTTP with an apply hook that run `nix flake check` & on the server end, a hook that runs `nix build` which not only checks the build, but also has the derivation in Nix store for me to pick up later as that server doubles as a substitutor. Collaboration can still be done via email of patches or DMing a pull request from someone else’s remote repo. It’s crazy how much we’ve been defaulting to tools that are so complicated--especially ones that require accounts to participate & have a social media features tacked on everywhere to cause the sorts of social media anxiety it does everywhere else. When the amount of collaborators is low, self-hosting is hardly a barrier that needs extra scaling.
Weird the author said email was a pain, but last patch I received it was as easy as `himalaya read --raw X | git am` to apply & pointing out that modern email clients do a bad job supporting this seems more damning of those clients than the workflow.
- misterio7 3y agoYou might want to try out self hosting hydra! It's pretty sweet for your usecase (building and caching Nix stuff, in a smart way). It can even run arbitrary commands (e.g. moving a release branch) EDIT: here's how I do it, in case it's useful: https://github.com/Misterio77/nix-config/blob/a74b2ede/hosts/celaeno/services/hydra/default.nix https://github.com/Misterio77/nix-config/blob/a74b2ede/hosts...
- toastal 3y agoCould be useful in the future for sure if I ever get to a point beyond pushing “trunk” :) …It would be great if darcs had Pijul’s channels …or Pijul’s CLI UX had parity with darcs