| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.4.7 to 0.4.8.
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](https://github.com/astral-sh/ruff/compare/v0.4.7...v0.4.8)
---
updated-dependencies:
- dependency-name: ruff
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This was a redundant rename and reduced the clarity of jobs when
querying from inside Grafana.
This rectifies that by renaming the stream to just `pods`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Copies the Metricity deployment manifest from the Metricity repo.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We currently used something like 1.2.3.4 or 1.1.1.1 as placeholder IP
addresses for DNS records where we ran in "originless" mode (the request
is always answered by a Cloudflare Worker or a redirect).
This changes that so we use designated reserved IPv4
addresses (192.0.2.0) to capture that traffic instead, ensuring that in
no circumstance would we leak traffic to an address like 1.1.1.1 or
1.2.3.4 if there was a Cloudflare misconfiguration.
Despite the potential risk vectors here being very small, it's a minor
change and also helps us ensure configuration works correctly in the future.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.4.5 to 0.4.7.
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](https://github.com/astral-sh/ruff/compare/v0.4.5...v0.4.7)
---
updated-dependencies:
- dependency-name: ruff
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
New collaborators:
DB1D650A Amrou Bellalouna <[email protected]>
The key has been verified and signed by both Joe and me. Chris was MIA
but approved it ahead of time.
Approved-by: Joe Banks <[email protected]>
Approved-by: Chris Lovering <[email protected]>
|
| | |
|
| | |
|
| | |
|
| | |
|