summaryrefslogtreecommitdiff
path: root/pkgs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* home: remove leanstuebinm2024-06-141-3/+0
| | | | | | | having tried multiple times, it's not actually very possible or reasonable to attempt to keep lean's version in sync with whatever mathlib requires at any given time, and probably better to have it just be managed by elan, no matter how annoying that may be.
* pkgs/apply-config: fixupsstuebinm2024-06-041-7/+8
| | | | | | | | | | the nix-env logic was still broken. It seems to have extremely weird failure modes under which it does not report errors when doing nix-env --set, or else the switch-to-configuration.pl script does not properly install the boot loader entry when it was installed via --set instead of --install. I'm not entirely clear on why yet, will need some investigating.
* all: jump to nixpkgs 24.05stuebinm2024-06-043-6/+79
| | | | | | | | | | | | 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)
* pkgs/apply-config: random fixesstuebinm2024-05-281-6/+4
|
* tweaksstuebinm2024-05-131-0/+2
|
* erlang_nox everywherestuebinm2024-05-071-3/+1
| | | | | turns out these overrides are more convoluted than I expected, but I think (?) this should now actually catch all of them.
* custom apply config scriptstuebinm2024-05-063-0/+150
| | | | | | | | since nixos-rebuild does not support applying a built config (i.e. one on which eval-config has already been called) without flakes. I might or might not extend this into a more proper reimplementation of nixos-rebuild.
* yeet the nix flakesstuebinm2024-04-292-3/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* tests: test travelynx using upstream `prove` suitestuebinm2024-04-171-1/+1
| | | | | unfortunately, these tests seem to be broken at the moment? Or at least I cannot see where my packaging differs from the provided cpanfile.snapshot.
* travelynx 2.4.1 → 2.6.7stuebinm2024-04-171-66/+48
| | | | | quite a bunch of these packages now need manually adjusted build inputs (most often just adding TestSuite2) to make the tests not fail.
* package transport-validatorstuebinm2024-04-152-0/+146
| | | | | | | 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)
* element-web: use older emoji fontsstuebinm2024-04-141-2/+16
| | | | | thanks to networkException for demonstrating how to do this; I'd not have had the patience to figure out which files to replace otherwise.
* Revert "flora: test-deploy the mollysocket nixpkgs PR"stuebinm2024-04-031-2/+1
| | | | | | This reverts commit a86a04f9e26854ec967c46a6ad3f015364fb91a6. It has since been merged into nixpkgs master, and i'm unsure if i will continue using it.
* element-web: nicer coloursstuebinm2024-04-022-4/+5
|
* flora/element-web: correct patch for left side barstuebinm2024-03-291-7/+5
| | | | | | | 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)
* flora: schildichat-web → element-webstuebinm2024-03-282-0/+164
| | | | | | | | | | | | | 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 …
* help i wrote a matrix botstuebinm2024-03-271-0/+9
| | | | | | | 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.
* pkgs/scripts: monit->prometheus converterstuebinm2024-03-111-0/+140
| | | | | | | | | 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).
* flora: test-deploy the mollysocket nixpkgs PRstuebinm2024-03-101-1/+2
| | | | https://github.com/NixOS/nixpkgs/pull/278981
* home: add git annex remote for amatlstuebinm2024-03-071-0/+13
| | | | | the tool is still a bit rough, but it should work well enough for actual use (even if i have to restart xochitl afterwards)
* restructure & general cleanupstuebinm2024-03-0514-17/+131
| | | | | | | | - 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
* init mollysocket package, module, and deploy it on florastuebinm2024-03-042-0/+40
| | | | with thanks to networkException, who wrote the initial nix package.
* noms.ing: redirect webring.noms.ing → noms.ingstuebinm2024-02-291-1/+1
| | | | | since that website doesn't contain anything anyways, but people started linking to it.
* update inputsstuebinm2024-02-211-1/+1
|
* modules/bookwyrm: manage.py wrapper needs env filestuebinm2024-02-151-1/+5
| | | | otherwise it just fails to start with an error
* modules/bookwyrm: use environmentFile for secretsstuebinm2024-02-151-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 ...
* modules/bookwyrm: initstuebinm2024-02-141-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.
* pkgs/bookwyrm: allow setting .env settingsstuebinm2024-02-131-76/+80
|
* pkgs: init bookwyrmstuebinm2024-02-115-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
* new webring entriesstuebinm2024-01-292-0/+41
|
* nomsable webringstuebinm2024-01-135-1/+65
| | | | (just messing around for now)
* huh, looks like i bought another domainstuebinm2023-12-093-0/+25
|
* new haskell for bahnhof.namestuebinm2023-12-011-1/+1
|
* jump to nixos 23.11stuebinm2023-11-303-3/+108
|
* bahnhof.name haskell rewritestuebinm2023-11-151-11/+31
|
* package inwebstuebinm2023-11-031-0/+21
| | | | not tested, but like, why not? Might be fun playing around with it.
* desktop: hikari with debugstuebinm2023-10-282-0/+22
|
* some reorganising of //pkgsstuebinm2023-10-143-27/+34
|
* home: cleaned up old mu versionstuebinm2023-10-141-3/+0
|
* more radicle stuff (now with tui!)stuebinm2023-10-122-4/+20
|
* playing around with radicle.xyzstuebinm2023-10-123-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.
* update RusTeXstuebinm2023-10-092-249/+147
|
* ilex: setup for hikari hackingstuebinm2023-10-081-0/+8
|
* update inputsstuebinm2023-10-011-17/+1
|
* home: add lean4stuebinm2023-09-231-0/+18
|
* update inputsstuebinm2023-09-061-2/+2
|
* package matrix.tostuebinm2023-07-282-0/+31
| | | | | apparently the default homeserver this uses is not configurable??? … might hack around later
* package RusTeXstuebinm2023-07-182-0/+1358
|
* update bahnhof.namestuebinm2023-07-091-0/+4
|
* update pkgs (travelynx, glitchtip)stuebinm2023-07-013-33/+8
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-23 05:31:37 +0000