Just FYI: I just migrated @…'s code and conf file away from Github. Won't change anything in how it works, just didn't want you to be confused when the config file and code are suddenly on Codeberg.
@… passthrough copy and add the assets to your page!
https://github.com/zachleat/zachleat.c
Right, apparently there's a whole other set of dependencies now which only install if you do
> bundle config set with 'development'
Presumably someone would have said that if I was reading documentation at all.
That makes it install rubocop.
The damned snitch is complaining about my change leaving a variable unassigned though. 🙄 Godamn linter snitches.
I think I have finally™️ (for the third or so time) found myself a solution for :python: #Python development on :nixos: #NixOS that allows me to just work with #pythonPoetry et. al. as on other distros.
…#NixOS update after sleeping for one month on host floyd (lenovo x260) takes 1 hour and 15 minutes (despite new 2TB SSD). During that, the device is almost non-responsive for anything else.
Host jackson (with even a slightly larger setup) probably would need 5-10 minutes maximum (lenovo t490). (I do weekly updates there.)
Didn't had that update "performance" while using Xubun…
With #OCIO v2 it feels like I need to learn OCIO all over again. So many new features for color config files. At the same time we're seeing more and more shows that are using #ACES ap0 as a color space for deliveries but are not using the rest of the ACES workflow (display transforms). Instead they use …
I’ve always wanted someone to tell me I autocomplete them.
:awesome:
https://www.npmjs.com/package/aral
(That feeling when someone makes a Node package with your name. Hey, at least it’s not a German petroleum company…)
Can some :nixos: nix person please explain to me how I pin nixpkgs *without flakes* and *without channels* in my configuration.nix [1]?
I pinned myself a 'pkgs.unstable' attribute via nixpkgs.config.packageOverrides [2], but how do I pin that infamous pkgs (that appears everywhere at the top argument list) in configuration.nix (and all the other imports automatically of course)?
[1]
Looking at Akkoma a bit.
Install was pretty persnickety, editing nginx config files by hand and having to stop Nginx while fetching ssl certs.
Apparently it needs to recompile at the slightest tweak of the config files? Strange decision.
Not really clear why I have to use pleroma.instance in the middle of the config. Initialy tried changing that to the name of my new test instance but apparently it isn't that. I guess "pleremoa.instance" is some kind of legacy config template from before Akkoma forked? Maybe?
Media-uploads apparently not working without further configuration. Wasn't sure why it insisted I put that in a different domain-name and then never told me how to configure to use that.
Doesn't seem likely this is the easiest activitypub server to manage after all.