| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
this is the rust tool used by the french ministry for
transport (deployed at https://transport.data.gouv.fr/validation),
patched to not include the server mode it usually has (i don't want to
constantly compile another copy of actix-web)
|
|
|
|
|
| |
thanks to networkException for demonstrating how to do this; I'd not
have had the patience to figure out which files to replace otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
| |
I discovered `guix pull --news` recently and realised I barely ever keep
up with nixpkgs's change logs, so here's a thing which might help to
change that. It's actually a little more general than I thought it'd
need to be — turns out that people do change old release notes items in
nixpkgs (mostly to update links), so it can format deletions as well.
(some vague inspiration was given by https://github.com/netj/markdown-diff)
It's a little cursed, but then so is using `lowdown` at all I'd say …
|
|
|
|
|
|
| |
thanks to change Id90e1e1ff399afe54fff68167f497f0484d2c218 being
merged into guix (d082573db1b86d922965dc746627bf0f0cc18af4), the
hikari package from upstream is no longer broken.
|
| |
|
|
|
|
|
|
| |
all non-nixos modules I use should have their documentation merged into
the configuration.nix man page I have available on ilex / abbenay, even
for modules not used there.
|
|
|
|
| |
because for some reason it's not there already
|
| |
|
|
|
|
|
| |
lowdown isn't very good, but at least it doesn't have any weird cloud
features (why is this the standard for things that show text??)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit a86a04f9e26854ec967c46a6ad3f015364fb91a6. It has
since been merged into nixpkgs master, and i'm unsure if i will continue
using it.
|
| |
|
| |
|
|
|
|
|
|
|
| |
without this, there's lots of extra space since the in-javascript layout
script thinks boxes take up more space than they actually do
(i think there was this nice idea, once, about separating the UI from
the rest of the application? ah well)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
since schildichat-web has essentially been unmaintained for a while now,
i guess i don't really have any choice here.
I've tried to at least hack a little css into my element so it won't
bother me too much (mostly making UI elements smaller & changing some
colours). However, it turns out they do UI calculations in javascript
which just make hard assumptions over values set in the css, and so far
I've not succeeded in fixing these.
Das ist doch wirklich alles Unsinn in diesem Ökosystem …
|
|
|
|
|
|
|
| |
not sure if this is a good idea or not, but i always liked how the
IRC #voc-wok channel of the c3voc works, and I don't run my own IRC (nor
do i want to have my monitoring on infra that is not my own), so I built
a similar thing with matrix.
|
|
|
|
| |
also remove v4l2loopback on ilex
|
|
|
|
| |
let's see if this hydra of mine is of any use :)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so I added a command to search though them :)
Should help whenever I'm not sure if I have cloned something already.
Intended usage is something like `cd (git where)`. It might be useful to
extend this so it doesn't assume everything has a remote called
`origin', but looks like my only three git repos which don't have
one (and which are not my own) where cloned via heartwood/radicle, and
I'm unlikely to need those again tbh.
… tbh, it might also be worth it to add a mass-fetch command? So much of
what I've cloned is just old stuff lying around …
|
|
|
|
|
|
|
|
|
| |
Not sure yet how much (if anything) I'll actually do with this, but it
seemed like a fun idea to try and it's been way to long since I wrote
anything in scheme.
Entirely untested, as I don't actually have a prometheus running atm
(apart from the one specifically for tracktrain on chaski).
|
|
|
|
|
|
| |
new feature which made this relevant is use of interactive sudo (since
abbenay still has interactive sudo from the days when it was a desktop
machine)
|
|
|
|
| |
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.
|