-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dealing with non-root $PWD #26
Comments
In some cases (where you are providing services to external users to be run via, say, If we are using flake-root to solve this, then there should be a way to disable it, such as via a |
How about resolving the dir in the following order:
|
👍 |
I'm happy to add support for setting The problem with resolving dir in an order like this is that the behaviour is no longer deterministic within the process-compose configuration. If you use flake-root, it behaves one way. If you don't, the same |
Maybe this should be solved upstream, in |
Is this really a problem that's worth solving in process-compose-flake / services-flake? I'm getting convinced that we should not. And instead document this, pointing users towards using mission-control + flake-root for a devShell experience. |
This creates the data diretory in
./example/tmp/data
(instead of./example/data
as one would expect -- ie. in flake root). What is the best way to address this? In nammayatri we useflake-root
+mission-control
module to side-step the problem.One possible solution here is to have services-flake require the use of
flake-root
module, and have the data directory use the flake root directory determined by the latter module.The text was updated successfully, but these errors were encountered: