nixfiles - my nixfiles

	Commit message (Collapse)	Author	Files	Lines
2024-02-15	modules/bookwyrm: manage.py wrapper needs env file	stuebinm	1	-1/+5
	otherwise it just fails to start with an error
2024-02-15	modules/bookwyrm: use environmentFile for secrets	stuebinm	1	-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-14	modules/bookwyrm: init	stuebinm	1	-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-13	pkgs/bookwyrm: allow setting .env settings	stuebinm	1	-76/+80

2024-02-11	pkgs: init bookwyrm	stuebinm	5	-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-29	new webring entries	stuebinm	2	-0/+41

2024-01-13	nomsable webring	stuebinm	5	-1/+65
	(just messing around for now)
2023-12-09	huh, looks like i bought another domain	stuebinm	3	-0/+25

2023-12-01	new haskell for bahnhof.name	stuebinm	1	-1/+1

2023-11-30	jump to nixos 23.11	stuebinm	3	-3/+108

2023-11-15	bahnhof.name haskell rewrite	stuebinm	1	-11/+31

2023-11-03	package inweb	stuebinm	1	-0/+21
	not tested, but like, why not? Might be fun playing around with it.
2023-10-28	desktop: hikari with debug	stuebinm	2	-0/+22

2023-10-14	some reorganising of //pkgs	stuebinm	3	-27/+34

2023-10-14	home: cleaned up old mu version	stuebinm	1	-3/+0

2023-10-12	more radicle stuff (now with tui!)	stuebinm	2	-4/+20

2023-10-12	playing around with radicle.xyz	stuebinm	3	-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-09	update RusTeX	stuebinm	2	-249/+147

2023-10-08	ilex: setup for hikari hacking	stuebinm	1	-0/+8

2023-10-01	update inputs	stuebinm	1	-17/+1

2023-09-23	home: add lean4	stuebinm	1	-0/+18

2023-09-06	update inputs	stuebinm	1	-2/+2

2023-07-28	package matrix.to	stuebinm	2	-0/+31
	apparently the default homeserver this uses is not configurable??? … might hack around later
2023-07-18	package RusTeX	stuebinm	2	-0/+1358

2023-07-09	update bahnhof.name	stuebinm	1	-0/+4

2023-07-01	update pkgs (travelynx, glitchtip)	stuebinm	3	-33/+8

2023-06-30	update inputs	stuebinm	7	-53/+3

2023-06-17	use dbus with x11, no x-less system for me i guess :(	stuebinm	1	-1/+1
	constantly rebuilding the world just got too annoying
2023-05-29	no libX11 on chaski (experimental)	stuebinm	1	-1/+3
	might have to revert this if it causes problems, or if rebuilding all the things annoys me too much.
2023-05-29	downgrade mu to unbreak mu4e / mail in emacs	stuebinm	1	-1/+3

2023-05-29	initial jump to nixos 23.05	stuebinm	4	-9/+42

2023-05-11	update bahnhof.name	stuebinm	1	-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-28	typst: v23-03-28 → v0.3.0	stuebinm	1	-3/+2

2023-04-26	bahnhof.name	stuebinm	1	-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-25	update inputs	stuebinm	1	-1/+1

2023-04-14	package travelynx because why not?	stuebinm	2	-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-07	typst: bump to v23-03-28	stuebinm	1	-7/+2

2023-04-01	add module for crs-tracker, for fun	stuebinm	3	-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-22	get rid of crane & naersk	stuebinm	2	-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-22	package typst	stuebinm	2	-0/+25

2023-03-22	package glitchtip	stuebinm	3	-0/+117
	i don't know why i did this. i literally have no use for it.
2023-03-04	home: a couple more packages	stuebinm	1	-0/+2

2023-03-02	add a default overlay, package the galmon.eu tools	stuebinm	2	-0/+53

2022-01-20	restructuring directories	stuebinm	2	-49/+0

2021-08-19	workadventure: use exneuland backend	stuebinm	1	-0/+32

2021-06-24	nixpkgs 20.09 → nixpkgs 21.05	stuebinm	1	-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-23	update sources	stuebinm	1	-1/+2

2021-03-08	Added Pleroma	stuebinm	1	-5/+5
	This pleroma config should be able to set itself up without any manual intervention (modulo the secrets file, which is almost empty). Annoyingly, the pleroma nixpkg is built from the pipeline artifacts of the pleroma gitlab and does not have support for pleroma's ssh/bbs mode.