Skip to content
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

Absolute /work directory is difficult to work with. #2

Open
dblotsky opened this issue Jul 10, 2017 · 2 comments
Open

Absolute /work directory is difficult to work with. #2

dblotsky opened this issue Jul 10, 2017 · 2 comments

Comments

@dblotsky
Copy link
Contributor

By default, might it be better to have something like ./work? If an absolute path is needed, would something like ~/.smtrecords work?

@dblotsky
Copy link
Contributor Author

Also, it doesn't seem like the directory is created by default (as far as I noticed). Should it be?

@mtrberzi
Copy link
Owner

The intent is that the directory is given with an absolute path because, in the "intended" mode of operation, the directory is picked up and used by workers in a distributed environment, and the workers are accessing a shared filesystem.

I'd like to fix this so that only workbase needs to be specified in the configuration, and everything is taken relative to that path. A reasonable default could be ~/.smtrecords as you suggest, which could be created if it doesn't exist (that doesn't happen right now because I assume you've done something to set this directory up in advance if it's a shared FS).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants