| Commit message (Collapse) | Author | Files | Lines |
|---|
|
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.
|
|
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).
|
|
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)
|
|
- 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
|
|
with thanks to networkException, who wrote the initial nix package.
|
|
since that website doesn't contain anything anyways, but people started
linking to it.
|
|
|
|
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.
|
|
|
|
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
|
|
|
|
(just messing around for now)
|
|
|
|
|
|
|
|
|
|
not tested, but like, why not? Might be fun playing around with it.
|
|
|
|
|
|
|
|
|
|
this packages the heartwood cli tools, the radicle web interface, and
runs a small example deployment on chaski.
TODO: decide if i want to keep this thing, then add declarative config
of the web interface, `rad auth`, and the radicle node to a NixOS
module; the current state is kinda suboptimal to deploy.
|
|
|
|
|
|
|
|
|
|
|
|
apparently the default homeserver this uses is not configurable???
… might hack around later
|
|
|
|
|
|
|
|
|
|
constantly rebuilding the world just got too annoying
|
|
might have to revert this if it causes problems, or if rebuilding all
the things annoys me too much.
|
|
|
|
|
|
setting elixir = elixir_1_14 may get me trouble later, we'll see
(version bounds on bahnhof.name's search engine are weird)
|
|
|
|
in gleam, because why not?
(tbf i will probably eventually rewrite this in a more sensible
language; I haven't even found any reason to use any of the OTP features
for this 🙈)
|
|
|
|
this file has been lying around for a bit over a year now, but I got
asked about it, so time to put it in the public repo I guess (& also
update it; it's on the most recent travelynx commit as of this writing).
|
|
|
|
please no one like, actually use this. unless you volunteer to at least
add a script to run database migrations, since currently these need to
be run by hand …
|
|
the only thing this makes more complicated is typst; most of the other
benefits I don't use in any case.
|
|
|
|
i don't know why i did this. i literally have no use for it.
|
|
|
