Systemd service unit template only works with root-dir layout

[natefoo]

This is because it consumes galaxy_root. On other layouts we should use a sensible default.

[hexylena]

urgh, curse of the configuration matrix. yea we should fix that. I wish we had data for how many people actually used things other than root-dir, because I suspect it's 1% of folks.

[natefoo]

You kinda shouldn't use root-dir for network filesystems though, as there is a lot of stuff that is better kept local. I actually was trying to come up with a new standard layout that properly splits things up for a standard secured network deployment but it's trickier than I expected.

[nuwang]

This would be great @natefoo. The k8s deployments could also benefit from this, especially when dispatching to existing clusters.

[dometto]

What is currently the recommended layout to use if you would like to have the datadir on NFS?

I'm managing to do so with a custom layout, but am running into this issue. Is there currentlt a good workaround for this issue? Would it be possible to simply pass in a different value into the systemd template when galaxy_root is not set?

I can still get everything to work by setting galaxy_manage_systemd to false, and then manually running galaxyctl start, which bootstraps the systemd services. But it feels counterintuitive to set galaxy_manage_systemd to false.