Make the ACT tracker friendly to external devs #212
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
Replaces many production-specific settings with more flexible values that need not be set or need not be exactly the same as a production machine.
Make the README almost accurate, WRT ease of starting up a new instance. Sqlite3 works just fine, if we enable it and refrain from using some psqlisms and some advanced features like window function ROW_NUMBER (which is in sqlite3, but not the version that's widely distributed yet).
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.
The ACT tracker had several things that made it hard to follow the README.
After this, anyone should be able to clone-load-run in three commands on a fresh, empty machine and have a working web site, and get immediate feedback.
Migrations are independent of database type. Settings have sensible, optional defaults (like sqlite for data backing).
One caveat is that the
compute_ranksfunction had a CTI expression that was a bit bewildering to me, and I assumed things were actually simpler than the CTI suggests it should be. Windowing over date makes it seem like it stores historical data, and this no longer updates historical data.