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

Support nested directories #26

Open
Seanstoppable opened this issue Feb 12, 2016 · 2 comments
Open

Support nested directories #26

Seanstoppable opened this issue Feb 12, 2016 · 2 comments

Comments

@Seanstoppable
Copy link

Common strategy is to have a 'schema' directory in the root of a repository.

However, using sem-add from the root puts the file in /scripts, rather than /schema/scripts

@mbryzek
Copy link
Owner

mbryzek commented Apr 2, 2016

One implementation of this would be to look for a:

".sem"

configuration file in the current working directory. If found, read the configuration and in there we'd have one key:

scripts_dir=./schema/scripts

By default this would be "./scripts" for backwards compatibility.

Any other thoughts for possible implementation?

@Seanstoppable
Copy link
Author

Yeah, that was essentially my thought.

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

No branches or pull requests

2 participants