It does not seem like this adds a NixOS module. I am unsure how useful this package is without a module.

will make it to an WIP, and add the module for it

We can merge the package first, without a module. It can still be useful to people who write their own configuration (non-reusable modules), or even to people who don’t run NixOS.

I'm still unsure of the way of handling the storage directory and the config file

Don’t do either in the package — the NixOS module should handle those.

I'm still unsure of the way of handling the storage directory and the config file

Don’t do either in the package — the NixOS module should handle those.

What I ment are both of the symlinks one pointing to etc, and one pointing to /var/lib

I'm still unsure of the way of handling the storage directory and the config file

Don’t do either in the package — the NixOS module should handle those.

What I ment are both of the symlinks one pointing to etc, and one pointing to /var/lib

The symlinks in the derivation look fine to me.

What I ment are both of the symlinks one pointing to etc, and one pointing to /var/lib

The symlinks in the derivation look fine to me.

@Mic92 look at the code. There are two symlinks that are basically no-ops AFAICT because they link to the build directory in the installPhase.

@alyssais which two? I only have three symlinks, one to /var/lib/engelsystem one to /etc/engelsystem/config.php and one to the migrate script inside the package. all three are working on my side

@Mic92 look at the code. There are two symlinks that are basically no-ops AFAICT because they link to the build directory in the installPhase.

Those symlinks are than copied to $out with the rest of the source later, so this is correct.

I'm just implementing the module for it, becaus I probably have to change the migrate script for that. The proplem I have is how to escape '' in a '' ... '' block?

I found this solution, but it seems ugly: '${""}'

Works in my prod env, without any user setup, besides changing the admin pass via the web interface

@GrahamcOfBorg test engelsystem

@Kloenk I fixed some small issues and added a test. If you want to squash the fixes into your commit, I'm fine with that - I just didn't want to get rid of your gpg signature. The test should probably stay in its own commit, though. :)

@talyz I like the changes. Should I squash them to make git log cleaner, or is that not needed?

Yeah, squash the fixes, but not the test.

Squashed. Can someone write ofborg to restest it?

@GrahamcOfBorg test engelsystem

Great work! Thanks! 👍