I recently got around to installing an OS on my home server, and setting up an Ansible playbook to manage the basic config.
mDNS is working, so I can access it at server.local on my network.
What’s next? Many ideas, but I think setting up docker and using it to run @… is on the short list.
Would be lovely to have a second copy of my git repos at ho…
I finally beefed up my :nix: #nix derivation for the :gitannex: #gitAnnex standalone builds so the download process of the non-predictable version url is automated. It now uses git annex itself to retrieve the tarball from a matching commit in @…
Here‘s a little tip if you’re using (the latest version of) Helix Editor:
Add the following keybinding to your config (if you don’t use Ctrl b for page up, that is; otherwise, change the key):
[keys.normal]
C-b = ":echo %sh{git blame -L %{cursor_line}, 1 %{buffer_name}}"
Now, when you press Crtl b in the editor, you’ll see the git blame for the line you’re on. Very useful for seeing which commit the line last changed in and, for teams, who committed the chang…
Is there sandbox weirdness going on with :nixos: #nix fixed-output-derivations (i.e. when you specify outputHash) that some tcp connections are disallowed? I can git clone in runCommand, but down the line a 'git annex get' (which internally just downloads another file via http) fails with this weird message 'no such protocol name: tcp'. With `--option sanbox false` everything is fine, …