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

install process v3 #40

Closed
jaesivsm opened this issue Apr 22, 2016 · 0 comments
Closed

install process v3 #40

jaesivsm opened this issue Apr 22, 2016 · 0 comments
Assignees
@jaesivsm
Labels
bug It's a bug ! Preventing normal use should be treated in priority. improvement major
Milestone
Madrid

Comments

@jaesivsm
Copy link
Owner

Installation is way better this way (see #5) but still not perfect :

  • requirements really need to be in a separate file so upgrade process might not pass through the install.py script and just via a pip install --upgrade -r requierements.txt
  • default path for sqlite database is wrong, it shouldn't be in src/
  • documentation should be mentionning the ways to upgrade the databases (./manager.py db upgrade)
  • dumping a conf.py was a good idea but not a great one, it prevents from constructing packages with configuration located in /etc or something similar. conf.py should be reading from a yaml/json/whatev file
@jaesivsm jaesivsm self-assigned this Apr 22, 2016
@jaesivsm jaesivsm added bug It's a bug ! Preventing normal use should be treated in priority. improvement major labels Apr 22, 2016
@jaesivsm jaesivsm added this to the 1.0.1 - Divlyn milestone Apr 22, 2016
@jaesivsm jaesivsm modified the milestones: 1.0.2 - Madrid, 1.0.1 - Divlyn May 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaesivsm jaesivsm

Labels
bug It's a bug ! Preventing normal use should be treated in priority. improvement major
Projects
None yet
Milestone
Madrid
Development

No branches or pull requests
1 participant
@jaesivsm