| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
https://github.com/NixOS/nixpkgs/pull/278981
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
the tool is still a bit rough, but it should work well enough for actual
use (even if i have to restart xochitl afterwards)
|
|
|
|
|
|
|
| |
doggo is more maintained, can use IPv6, queries all nameservers at once
by default, and generally feels comfier.
(now if only it had a man page ..)
|
| |
|
|
|
|
|
|
|
|
| |
- pkgs/ should now also contain all package overrides
- pkgs/patches/ now contains all patches
- nix flake info succeeds again
- still not sure what to do about scripts
- services which are not used should not be kept around this long
|
|
|
|
|
|
| |
which has the nice side-effect that they now show up on my `man configuration.nix'.
(also I don't have to manually import things anymore)
|
|
|
|
| |
with thanks to networkException, who wrote the initial nix package.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
since that website doesn't contain anything anyways, but people started
linking to it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so it turns out ntfy can run a little smtp server, which monit can send
its alerts to, resulting in a halfway okayish monitoring setup. It
doesn't even require mucking about with `sendmail'!
Downside: this is still monit.
Upside: from what I've heard, the other monitoring tools don't actually
seem to be all that much better?
Now I only have to come up with reasonable checks for the stuff I want
to actually keep an eye on …
|
|
|
|
|
| |
though it seems a little blurry at low resolutions. might have to tweak
stuff / see if i can find a better font.
|
| |
|
| |
|
| |
|
|
|
|
| |
because like, why not learn how to use these out-of-tree?
|
|
|
|
| |
otherwise it just fails to start with an error
|
|
|
|
|
|
|
|
|
|
| |
this allows setting options via an environment file that is passed to
the systemd units, in addition to the ones set during build time of the
package.
For now this is tailored to SECRET_KEY, but it may be useful for other
settings as well (e.g. EMAIL_HOST_PASSWORD), and I'm not sure if it
takes priority over the build-time settings ...
|
| |
|
|
|
|
|
|
|
|
| |
this should be mostly usable for actual deployments. Only thing that's
really still annoying is having to set the SECRET_KEY via Nix, since
not having set it makes the package fail to build. But it doesn't
actually end up in the derivation, so changing it afterwards should be
fine; I've just not tested that yet.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
for Chris Marten's logic course. Uses an unofficial version from github
since the actually released version is so old that the elisp code for
the emacs mode doesn't work with an up-to-date emacs anymore.
|
|
|
|
| |
(except for man pages — without these, somehow deploy-rs breaks)
|
| |
|
|
|
|
|
|
|
| |
this is still missing:
- a nice way to do settings
- lots of testing (run the manage.py test script in a nixos test?)
- an actual way to deploy this in a halfway reasonable way
|
| |
|
|
|
|
|
|
|
|
| |
initial config, the system is now a mess with lots of old nix stuff
still hanging out on the disk.
Tbh not sure if I'll do much with this, but wanted to play around a
little with this again.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
something something nftables module obscurity
|
| |
|
|
|
|
|
|
| |
turns out there's an issue for that:
https://github.com/sharkdp/bat/issues/2563
and even a hint in bat's README.md
|
| |
|
|
|
|
| |
they sometimes hang until akkoma gets reaped by the oom killer
|
| |
|
|
|
|
| |
(just messing around for now)
|
| |
|
| |
|
| |
|
| |
|
| |
|