Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions .github/workflows/registry.yml

This file was deleted.

5 changes: 2 additions & 3 deletions .graphite.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ projects:
tags: [django, postgresql, redis, celery, docker]
owner: amrmscll
authors: [AmrMsCLL]
status: live
status: archived
listed: true
showcase:
problem: >
Expand All @@ -29,5 +29,4 @@ projects:
Defined the test scenario and owns the deployment, infrastructure and acceptance
criteria used to validate the Graphite hosting path.
deploy:
kind: compose
host: message-lab.project-graphite.com
kind: none
21 changes: 11 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,19 +58,20 @@ Messages are stored and read by the administrator. Do not enter private or sensi

## Deployment

Production runs at https://message-lab.project-graphite.com from
[`deploy/graphite-message-lab/values.yaml`](https://github.com/project-graphite/platform/blob/main/deploy/graphite-message-lab/values.yaml) in `platform`.
A push to `main` publishes the `web` and `worker` images and records their tag there, which deploys
them. PostgreSQL and Redis persist in named volumes, migrations run before Gunicorn starts, and the
whole stack sleeps after 30 minutes without visitors and wakes on the next request.
`SECRET_KEY` and `POSTGRES_PASSWORD` are in the organisation's secrets repository.
Retired. Message Lab proved the Project Graphite deploy path end to end, and its one feature now
lives in Graphite Hub as the messages wall at
[project-graphite.com/messages](https://project-graphite.com/messages). Nothing runs at
`message-lab.project-graphite.com`: the registry entry in `.graphite.yml` is `archived` with
`deploy: none`, and `platform` has no `deploy/graphite-message-lab/` folder. The repository stays
as the case study and runs locally as above.

To create the first administrator, visit the site so it wakes, then open the `web` container's Terminal
in the [Graphite Console](https://console.project-graphite.com) (or `docker exec` into it on the VPS)
and run:
A push to `main` still publishes the `web` and `worker` images to GHCR; the deploy job then finds
no deploy folder in `platform` and records nothing, by design.

To create an administrator locally:

```sh
python manage.py createsuperuser
./run manage createsuperuser
```

## Attribution
Expand Down
Loading