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

Move reports to database #242

Closed
bagofarms opened this issue Feb 24, 2017 · 2 comments
Closed

Move reports to database #242

bagofarms opened this issue Feb 24, 2017 · 2 comments
Assignees
@emilysachs
Labels
enhancement high priority

Comments

@bagofarms
Copy link
Member

The entirety of a report should be stored in a database field instead of on disk. This will make UDOIT compatible with load-balanced or multi-worker environments (like using multiple dynos in Heroku).
@bagofarms
Copy link
Member Author

This should also include removing the .gitkeep file from the existing reports folder.

@emilysachs emilysachs self-assigned this Mar 2, 2017
emilysachs added a commit that referenced this issue Mar 7, 2017
@emilysachs
Saves JSON directly into database in new column, tests which column t…
f88f669 
…o use when viewing old reports, creates new databases without file path, issue #242
@emilysachs emilysachs mentioned this issue Mar 7, 2017
Merged
This was referenced May 8, 2017
Closed
Closed
@bagofarms
Copy link
Member Author

Fixed in 2.2.0 and improved in 2.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@emilysachs emilysachs

Labels
enhancement high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bagofarms @emilysachs