Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Update site deployment | 2025-07-18 | -1/+1 | |
| | ||||
* | Update ingresses with NGINX ingress upgrade | 2025-04-05 | -3/+3 | |
| | ||||
* | Update from command to args in site deployment | 2024-06-07 | -1/+1 | |
| | | | | | | | | Kubernetes renames ENTRYPOINT in Docker images to command and any additional args go in `args` (confusing, I know!) This ensures that we run within the context of Poetry so can reach Django and other installed requirements when running migrations. | |||
* | Remove unnecessary shell execution for migration initContainer | 2024-06-07 | -3/+3 | |
| | ||||
* | Update site to run migrations in an init container | 2024-06-07 | -0/+13 | |
| | | | | | | | | | | | | | | | | | | In accordance with updates from python-discord/site#1338 this changes the way migrations are run. Previously, migrations would be run all from within the manage.py execution process with the command being manually spawned using Django internals. After python-discord/site#1338 merges the Dockerfile will directly invoke gunicorn and bypass manage.py to simplify the process and avoid problems with shared database contexts. Hence, we need to manually run migrations using an init container. With testing there is no additional delay in doing this as spinning up an init container is cheap and we don't cut over any traffic until the site passes a healthcheck anyway. | |||
* | Update site secret with new database address | 2024-06-01 | -0/+0 | |
| | ||||
* | Update site and metricity with new metricity db user credentials | 2024-05-28 | -0/+0 | |
| | ||||
* | Update all secrets to new PostgreSQL service | 2024-04-27 | -0/+0 | |
| | ||||
* | Move site namespace | 2024-04-15 | -0/+172 | |