| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
| datasource | package | from | to |
| ---------- | ------- | ---- | ---- |
| docker | ghost | 5.87 | 5.88 |
|
|
|
|
|
|
| |
| datasource | package | from | to |
| ---------- | ------- | ---- | ---- |
| docker | ghost | 5.78 | 5.87 |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|