List view
Over time we've duplicated much of the built-in Django functionality with our aging Flask+Jinga+SQLAlchemy stack. Our current stack is now 4 years old and at least one major version behind the current release of those core dependencies. We've also struggled with pinpointing a memory leak in our Heroku env with our current stack, and we suspect some tertiary dependency library is leaking. So we think a port to Django 4.x is an appropriate strategy for updating and streamlining our stack. The work will be performed in a [new repo](https://github.com/BlueprintKansas/v3.ksvotes.org). The existing repo will be retained after the cutover. We'll migrate any existing Issues as necessary.
No due date•2/2 issues closednew and updated forms are available. they need to be: * copied to the s3 bucket * coordinates confirmed via testing
No due date•4/4 issues closed