This reverts commit eabfb55de4.
The issues doesn't seem to be the number of generations,
but that nixos itself keeps all channels as gc roots.
This prevents proper cleanup of old channel data.
This is useful in order to remember the actual command.
The necessary environment arguments need to be set.
This can be executed from within a functional-* folder.
phpactor was added to upstream.
This only included the lsp usable package, not vim plugin.
I no longer need my own build script as I now use the upstream version.
That way I benefit from all the maintenance and updates.
I use the package source to build the neovim plugin.
podman-compose has some issues on ubuntu and with volumes.
I'll keep docker-compose.
But I prefer podman for t3docs rendering as it doesn't fuck up the file
permissions.
The os update and backup now include etckeeper as its part of the
workflow.
The os updates now have the same name on all systems. That should reduce
friction, same command for same workflow, just different implementation.
Nix adds errexit and failpipe.
Using head will end in 141 SIGPIPE, see: https://unix.stackexchange.com/a/580119/185477
I apply the workaround / fix as suggested on StackExchange.
That way the script runs and can execute the cleanup and diff.
This allows to set environment for whole session.
Way better than sending explicit export commands in different shells.
This also allows each new pane to inherit the same environment.
Those tools are expected to be globally available.
Defining runtime input will not expose system wide versions but link
specific versions.
Updating the packages will not update within the environment as custom
project starts a tmux session with the inherited runtime inputs.
Respect new folder structure for reuter.
Move variable initialization into section. Do not initialize if we
already can attach to a session.
Remove legacy database handling. Instead fetch customer name from file
path and concatenate project and customer to database name. This also
supports more deeply nested folder structure within customer folder.
Use writeShellApplication and adjust code to pass shellcheck.
Remove unnecessary overhead after migrating to writeShellApplication.
This involves binary paths as they are imported.
Also rename to custom-project to follow my naming scheme for custom
scripts.
