programmatically place generated files in development environment
fricklerhandwerk
pushed to generated-code at fricklerhandwerk/Fediversity
2025-04-22 16:34:19 +02:00
programmatically place generated files in development environment
fricklerhandwerk
created branch generated-code in fricklerhandwerk/Fediversity
2025-04-22 16:25:58 +02:00
fricklerhandwerk
pushed to generated-code at fricklerhandwerk/Fediversity
2025-04-22 16:25:58 +02:00
fricklerhandwerk
pushed to generate-module-options at fricklerhandwerk/Fediversity
2025-04-22 14:38:02 +02:00
Change key for Niols
fricklerhandwerk
deleted branch prepare-refactor from fricklerhandwerk/Fediversity
2025-04-22 11:30:37 +02:00
deployment module: set configuration explicitly
deployment module: set configuration explicitly
fricklerhandwerk
created branch prepare-refactor in fricklerhandwerk/Fediversity
2025-04-22 10:02:12 +02:00
fricklerhandwerk
pushed to prepare-refactor at fricklerhandwerk/Fediversity
2025-04-22 10:02:12 +02:00
unify versioning (minus around nixops, for now)
At this point we may set up our own little module system class to pass around sources
. But I see this is trying to work around flake-parts, so either we rip out flake-parts or embrace it.
unify versioning (minus around nixops, for now)
This can't work, you're missing the argument to nixpkgs
.
Backups for Forgejo
This is not a user story though, it's about infrastructure for development here.
ProxmoX back-end supports multiple users
The data model already allows multiple deployments per operator, so this is merely a UI issue.