Code stability Polis stock for PolisNL SAAS #64
Labels
No labels
BZK
Backlog
Bug
Prio 1
Prio 2
Prio 3
RC
Testing
WIP
auth
doc
feature
frontend
idea
integration
math
ops
bug
duplicate
enhancement
question
testing
verify
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
BetaBreak/voxit-project#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Freeze (for x months) a production stable version of latest https://github.com/compdemocracy/polis/tree/stable. To have a working docker-compose with PolisNL reference frontend.
Stock Polis gets updated, but merges are squashed. The fixes and new features are applied to the codebase in bulk. This will break the PolisNL deployment.
To prevent deployment breakage we should use the code of a release https://github.com/compdemocracy/polis/tree/stable and make it work with our frontend code and freeze the backend Polis code for e.g. a half year.
changed the description
changed the description
mentioned in issue #69
assigned to @gberh
Our Polis containers have been reverted to polis revision 604ae7c in particiapp/polis@e18cbc3. This still requires some more testing.
Due to the recent development direction of Polis future regular updates seem increasingly unlikely and undesirable.
I've moved the used Polis revision forward to
fd440c3in particiapp/polis@bd2c0381 which is the last commit before Polis introduced a hard dependency on DynamoDB in1681d6e.I have also found and fixed the cause of the broken report and visualization issue,
MATH_ENVhas to be set to "prod" explicitly. Contrary to what the documentation says it does not have a default for the server.