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.

Sign up for GitHub

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

Jump to bottom

Allow migrations to be run without cloned repository #31

Open
thejunglejane opened this issue Jan 26, 2016 · 1 comment
Open

Allow migrations to be run without cloned repository #31

thejunglejane opened this issue Jan 26, 2016 · 1 comment
Labels
enhancement help wanted

Comments

@thejunglejane
Copy link
Owner

To run the v1.0.0 database migrations, you need to have the datums repository cloned and need to be inside that cloned repository so alembic can find the alembic.ini file.
@thejunglejane thejunglejane added this to the v1.0.0 milestone Jan 26, 2016
@thejunglejane
Copy link
Owner Author

Thinking this is best achieved via a command line flag

$ datums --migrate

thejunglejane added a commit that referenced this issue Jan 31, 2016
@thejunglejane
Moved alembic migrations into datums/migrations. #31
4d95240
@thejunglejane thejunglejane removed this from the v1.0.0 milestone Jan 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thejunglejane