You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
upgrade dependencies and fix some things which broke
mysql fulltextsearch module doesn't work but nobody uses that
PyMySQL not upgraded due to
julien-duponchelle/python-mysql-replication#337
ES not really tested as always xd (I need to make a proper dev setup)
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ pyenv eases the use of different Python versions, and as not all Linux distros o
40
40
41
41
### Finishing up
42
42
- Run `python db_create.py` to create the database and import categories
43
-
- Follow the advice of `db_create.py` and run `./db_migrate.py stamp head` to mark the database version for Alembic
43
+
- Follow the advice of `db_create.py` and run `flask db stamp head` to mark the database version for Alembic
44
44
- Start the dev server with `python run.py`
45
45
- When you are finished developing, deactivate your virtualenv with `pyenv deactivate` or `source deactivate` (or just close your shell session)
46
46
@@ -51,16 +51,16 @@ Continue below to learn about database migrations and enabling the advanced sear
51
51
## Database migrations
52
52
- Database migrations are done with [flask-Migrate](https://flask-migrate.readthedocs.io/), a wrapper around [Alembic](http://alembic.zzzcomputing.com/en/latest/).
53
53
- If someone has made changes in the database schema and included a new migration script:
54
-
- If your database has never been marked by Alembic (you're on a database from before the migrations), run `./db_migrate.py stamp head` before pulling the new migration script(s).
55
-
- If you already have the new scripts, check the output of `./db_migrate.py history` instead and choose a hash that matches your current database state, then run `./db_migrate.py stamp <hash>`.
54
+
- If your database has never been marked by Alembic (you're on a database from before the migrations), run `flask db stamp head` before pulling the new migration script(s).
55
+
- If you already have the new scripts, check the output of `flask db history` instead and choose a hash that matches your current database state, then run `flask db stamp <hash>`.
56
56
- Update your branch (eg. `git fetch && git rebase origin/master`)
57
-
- Run `./db_migrate.py upgrade head` to run the migration. Done!
57
+
- Run `flask db upgrade head` to run the migration. Done!
58
58
- If *you* have made a change in the database schema:
59
59
- Save your changes in `models.py` and ensure the database schema matches the previous version (ie. your new tables/columns are not added to the live database)
60
-
- Run `./db_migrate.py migrate -m "Short description of changes"` to automatically generate a migration script for the changes
60
+
- Run `flask db migrate -m "Short description of changes"` to automatically generate a migration script for the changes
61
61
- Check the script (`migrations/versions/...`) and make sure it works! Alembic may not able to notice all changes.
62
-
- Run `./db_migrate.py upgrade` to run the migration and verify the upgrade works.
63
-
- (Run `./db_migrate.py downgrade` to verify the downgrade works as well, then upgrade again)
62
+
- Run `flask db upgrade` to run the migration and verify the upgrade works.
63
+
- (Run `flask db downgrade` to verify the downgrade works as well, then upgrade again)
0 commit comments