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.

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

Deployment streamlining #233

merged 24 commits into from Apr 12, 2021

Deployment streamlining #233

merged 24 commits into from Apr 12, 2021


Copy link

@loleg loleg commented Mar 14, 2021

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_MIGRATE environment 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!

@loleg loleg requested a review from gonzalocasas March 16, 2021 11:06
Copy link
Collaborator Author

loleg commented Mar 16, 2021

Tests passing & deployed for testing to

@loleg loleg merged commit bde8e7d into dribdat:main Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant