aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/namespaces/web (follow)
Commit message (Collapse)AuthorAgeLines
* Update site deploymentGravatar Joe Banks2025-07-18-1/+1
|
* Update ingresses with NGINX ingress upgradeGravatar Joe Banks2025-04-05-5/+5
|
* Remove ghost blogGravatar Chris Lovering2024-07-22-99/+0
|
* chore(deps): update ghost docker tag to v5.88Gravatar renovate[bot]2024-07-22-1/+1
| | | | | | | datasource | package | from | to | | ---------- | ------- | ---- | ---- | | docker | ghost | 5.87 | 5.88 |
* chore(deps): update ghost docker tag to v5.87Gravatar renovate[bot]2024-07-18-1/+1
| | | | | | | datasource | package | from | to | | ---------- | ------- | ---- | ---- | | docker | ghost | 5.78 | 5.87 |
* Update Pinnwand logo to square imageGravatar Joe Banks2024-06-09-1/+1
|
* Update from command to args in site deploymentGravatar Joe Banks2024-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 initContainerGravatar Joe Banks2024-06-07-3/+3
|
* Update site to run migrations in an init containerGravatar Joe Banks2024-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 addressGravatar Joe Banks2024-06-01-0/+0
|
* Update site and metricity with new metricity db user credentialsGravatar Joe Banks2024-05-28-0/+0
|
* Update pinnwand conenction string to point at lovelaceGravatar Chris Lovering2024-05-16-0/+0
|
* Remove temporary testing deployment of pinnwandGravatar Chris Lovering2024-05-16-142/+0
|
* Deploy a pinnwand instance that used lovelace's pg database (#293)Gravatar Amrou Bellalouna2024-05-15-0/+142
| | | | | | | | | | | * add a deployment config for pinnwand on lovelace * add a dns entry for the new pastebin * Add database URI for pinnwand to connect to psql on lovelace --------- Co-authored-by: Chris Lovering <[email protected]>
* Update pinnwand database secret to support being ast.literal_eval'dGravatar Chris Lovering2024-05-13-0/+0
|
* Use our own fork for deploying pinnwandGravatar Chris Lovering2024-05-13-1/+1
|
* Update all secrets to new PostgreSQL serviceGravatar Joe Banks2024-04-27-0/+0
|
* Move ghost to web namespaceGravatar Joe Banks2024-04-15-0/+99
|
* Move pinnwand to webGravatar Joe Banks2024-04-15-0/+142
|
* Move public statsGravatar Joe Banks2024-04-15-0/+42
|
* Move site namespaceGravatar Joe Banks2024-04-15-0/+172