summaryrefslogtreecommitdiff
path: root/pkgs (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-03-04init mollysocket package, module, and deploy it on florastuebinm2-0/+40
with thanks to networkException, who wrote the initial nix package.
2024-02-29noms.ing: redirect webring.noms.ing → noms.ingstuebinm1-1/+1
since that website doesn't contain anything anyways, but people started linking to it.
2024-02-21update inputsstuebinm1-1/+1
2024-02-15modules/bookwyrm: manage.py wrapper needs env filestuebinm1-1/+5
otherwise it just fails to start with an error
2024-02-15modules/bookwyrm: use environmentFile for secretsstuebinm1-2/+4
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 ...
2024-02-14modules/bookwyrm: initstuebinm1-4/+46
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.
2024-02-13pkgs/bookwyrm: allow setting .env settingsstuebinm1-76/+80
2024-02-11pkgs: init bookwyrmstuebinm5-0/+185
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
2024-01-29new webring entriesstuebinm2-0/+41
2024-01-13nomsable webringstuebinm5-1/+65
(just messing around for now)
2023-12-09huh, looks like i bought another domainstuebinm3-0/+25
2023-12-01new haskell for bahnhof.namestuebinm1-1/+1
2023-11-30jump to nixos 23.11stuebinm3-3/+108
2023-11-15bahnhof.name haskell rewritestuebinm1-11/+31
2023-11-03package inwebstuebinm1-0/+21
not tested, but like, why not? Might be fun playing around with it.
2023-10-28desktop: hikari with debugstuebinm2-0/+22
2023-10-14some reorganising of //pkgsstuebinm3-27/+34
2023-10-14home: cleaned up old mu versionstuebinm1-3/+0
2023-10-12more radicle stuff (now with tui!)stuebinm2-4/+20
2023-10-12playing around with radicle.xyzstuebinm3-3/+76
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.
2023-10-09update RusTeXstuebinm2-249/+147
2023-10-08ilex: setup for hikari hackingstuebinm1-0/+8
2023-10-01update inputsstuebinm1-17/+1
2023-09-23home: add lean4stuebinm1-0/+18
2023-09-06update inputsstuebinm1-2/+2
2023-07-28package matrix.tostuebinm2-0/+31
apparently the default homeserver this uses is not configurable??? … might hack around later
2023-07-18package RusTeXstuebinm2-0/+1358
2023-07-09update bahnhof.namestuebinm1-0/+4
2023-07-01update pkgs (travelynx, glitchtip)stuebinm3-33/+8
2023-06-30update inputsstuebinm7-53/+3
2023-06-17use dbus with x11, no x-less system for me i guess :(stuebinm1-1/+1
constantly rebuilding the world just got too annoying
2023-05-29no libX11 on chaski (experimental)stuebinm1-1/+3
might have to revert this if it causes problems, or if rebuilding all the things annoys me too much.
2023-05-29downgrade mu to unbreak mu4e / mail in emacsstuebinm1-1/+3
2023-05-29initial jump to nixos 23.05stuebinm4-9/+42
2023-05-11update bahnhof.namestuebinm1-1/+2
setting elixir = elixir_1_14 may get me trouble later, we'll see (version bounds on bahnhof.name's search engine are weird)
2023-04-28typst: v23-03-28 → v0.3.0stuebinm1-3/+2
2023-04-26bahnhof.namestuebinm1-0/+13
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 🙈)
2023-04-25update inputsstuebinm1-1/+1
2023-04-14package travelynx because why not?stuebinm2-0/+231
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).
2023-04-07typst: bump to v23-03-28stuebinm1-7/+2
2023-04-01add module for crs-tracker, for funstuebinm3-0/+92
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 …
2023-03-22get rid of crane & naerskstuebinm2-6/+79
the only thing this makes more complicated is typst; most of the other benefits I don't use in any case.
2023-03-22package typststuebinm2-0/+25
2023-03-22package glitchtipstuebinm3-0/+117
i don't know why i did this. i literally have no use for it.
2023-03-04home: a couple more packagesstuebinm1-0/+2
2023-03-02add a default overlay, package the galmon.eu toolsstuebinm2-0/+53
2022-01-20restructuring directoriesstuebinm2-49/+0
2021-08-19workadventure: use exneuland backendstuebinm1-0/+32
2021-06-24nixpkgs 20.09 → nixpkgs 21.05stuebinm1-3/+1
Since pleroma is in nixpkgs 21.05, this requires some reshuffling to keep the unstable version of pleroma (otherwise the database versions are not compatible, and pleroma does not like database downgrades). Additionally, hedgedoc's database has been moved to a postgres user who is actually called hedgedoc.
2021-06-23update sourcesstuebinm1-1/+2