Deployment streamlining #233
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a pre-0.5.0 release PR with a number of code cleaning improvements in an effort to make dribdat more portable and maintainable. The focus is still on getting it quick and easy to deploy on Heroku, although I am also testing other platforms, and welcome suggestions on cloud-targets.
Due to continued issues with juggling buildpacks in Heroku, this version removes the dependency on nodejs in production by switching to CDN versions of key libraries. In development, local un-minified libraries are still referenced.
The Migrations folder is now again checked in, as per recommendation, with a basic initial migration and a strategy to keep legacy (use the
FORCE_MIGRATEenvironment variable, or manually reset Alembic) and new installations in sync.There is some minor usability improvement to the interface, in particular a basic default Bootswatch theme (Simplex) is used instead of plain Bootstrap. The navigation buttons now activate properly, and the menu has been slightly revamped from user feedback. The login button is now in the page footer.
All in all, a big, boring, but essential maintenance release. Happy hacking!