forked from hacc/haccfiles
stuebinm
285a8e6a8e
this depends on a whole lot of imperative nonsense being done at the same time, which i have done. of special interest to anyone attempting to understand this is https://docs.mattermost.com/deploy/postgres-migration.html for the general shape of incompetence at work, https://docs.mattermost.com/install/setting-up-socket-based-mattermost-database.html#with-unix-socket for yet another interesting syntax for database connection strings, and https://github.com/dimitri/pgloader/issues/782#issuecomment-502323324 for a truly astonishing take on how to do database migrations, which unfortunately i have followed. As far as I can tell, everything has kept working. Downtime was mostly spent understanding connection string syntax and their horribly buggy parsers. Note for people with server access: - i have kept the temporary files (including logs) around in /persist/migration inside the container should we ever need them again - there's a zfs snapshot @pre-postgres with the old state |
||
|---|---|---|
| .. | ||
| configuration.nix | ||
| forgejo.nix | ||
| hardware.nix | ||
| hedgedoc-hacc.nix | ||
| hedgedoc-i4f.nix | ||
| lxc.nix | ||
| mail.nix | ||
| mattermost.nix | ||
| monit.nix | ||
| murmur.nix | ||
| nextcloud.nix | ||
| nftables.nix | ||
| nginx-pages.nix | ||
| s4f-conference.nix | ||
| tracktrain.nix | ||
| uffd.nix | ||
| vaultwarden.nix | ||