-
Jan Mach authored
With future improvements of database schema there must be a mechanism for performing database migrations. Problem is we have two databases, one accesed via SQLAlchemy and the second directly via Psycopg2. I have selected to use Flask-Migrate plugin built on top of Alembic to perform metadata database migrations. (Redmine issue: #4230)
Jan Mach authoredWith future improvements of database schema there must be a mechanism for performing database migrations. Problem is we have two databases, one accesed via SQLAlchemy and the second directly via Psycopg2. I have selected to use Flask-Migrate plugin built on top of Alembic to perform metadata database migrations. (Redmine issue: #4230)
requirements.pip 482 B
pytz==2018.5
ply==3.11
pymongo==3.5.1
psycopg2>=2.7,<2.8 --no-binary psycopg2
babel==2.6.0
wtforms==2.2.1
sqlalchemy==1.2.10
jinja2==2.10
blinker==1.4
flask==1.0.2
flask-login==0.4.1
flask-mail==0.9.1
flask-migrate==2.2.1
flask-babel==0.11.2
flask-principal==0.4.0
flask-wtf==0.14.2
flask-script==2.0.6
flask-sqlalchemy==2.3.2
flask-debugtoolbar==0.10.1
geoip2==2.9.0
rrdtool==0.1.14
pydgets==0.9
pyzenkit==0.49
pynspect==0.16
ipranges==0.1.10
typedcols==0.1.13
idea-format==0.1.11