nixfiles - my nixfiles

	Commit message (Collapse)	Author	Files	Lines
2024-06-04	all: jump to nixpkgs 24.05	stuebinm	2	-14/+16
	this does a lot of things, most of which are maintenance: - sources update - adjust newly-renamed options - swap some packages that were removed / renamed - update nomsring to newer default ghc - remove the deprecated lib.mdDoc from modules/*.nix - disable the nixpkgs mollysocket module so my own keeps evaluating - bundle the package definition of hikari & wlroots 0.15, which nixpkgs has removed as unmaintained (in fairness, they are unmaintained)
2024-04-29	yeet the nix flakes	stuebinm	1	-0/+5
	this is, in the widest possible sense, a revert of e88fed18f499a3e8ac98c772bbb62f00d1f8d1d7, which was now a little over two years ago. Of course, lots of things have changed since then: - this uses npins instead of niv, which is both simpler and still maintained - i haven't brought back the old deploy lib; I still use deploy-rs (with some modifications) to deploy things - if you actually use my stuff downstream, you can now use packages/ & tests/ & modules/ as entry points directly, while still having some control over inputs - (since i also don't believe any downstream users actually exist, i've not bothered to have a shim flake.nix so your stuff probably just broke. well, it was an experimental feature, anyways) - in general there's a lot more of the old-fashioned structure back again, with default.nix files in subdirectories that form a structure, not like how almost everything was just imported in the one big flake.nix file For people who are interested in also having a non-flake config similar to this one, it's probably best to take a look at inputs.nix (and also at npins, of course)
2024-03-04	init mollysocket package, module, and deploy it on flora	stuebinm	1	-0/+92
	with thanks to networkException, who wrote the initial nix package.
2024-02-15	modules/bookwyrm: manage.py wrapper needs env file	stuebinm	1	-3/+4
	otherwise it just fails to start with an error
2024-02-15	modules/bookwyrm: use environmentFile for secrets	stuebinm	1	-8/+47
	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: whoops, that's not how the module system works	stuebinm	1	-14/+25

2024-02-14	modules/bookwyrm: init	stuebinm	1	-0/+140
	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.
2023-05-29	initial jump to nixos 23.05	stuebinm	1	-2/+2

2023-04-01	add module for crs-tracker, for fun	stuebinm	1	-0/+132
	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	a glitchtip module, because why not	stuebinm	1	-0/+81
	in case i ever think i need such a thing, i guess
2022-01-09	use flakes instead of niv & stuff	stuebinm	2	-59/+0

2021-03-08	Added Pleroma	stuebinm	1	-2/+6
	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.