Skip to content

Conversation

@ColonelThirtyTwo
Copy link
Contributor

@ColonelThirtyTwo ColonelThirtyTwo commented Nov 18, 2025

Optimize images and allow them to be ran standalone without needing to bind certain things from the GW source repo. Add a workflow to publish the images to GHCR.

See individual commits for descriptions of work.

Breaking change: This removes several exposed ports from the compose files. While most of these were redundant, users may have been using the PostgreSQL port for administration. The PostgreSQL database is still accessible via running commands in the Postgres Docker container, or by editing the compose files to re-expose the port.

marcpfuller
marcpfuller previously approved these changes Nov 18, 2025
@ColonelThirtyTwo ColonelThirtyTwo changed the title DRAFT: Improvements to docker images Improvements to docker images Dec 2, 2025
@ColonelThirtyTwo ColonelThirtyTwo changed the title Improvements to docker images Improve and publish docker images Dec 5, 2025
Rather than having the Django entrypoint script wait for postgres to
start, use Docker's `depends_on` `service_healthy` condition. Slims
down the entrypoint script.
Neither should be copied over - node_modules causes errors when copying
and should be downloaded inside of the container, while pycache files
are build artifacts.
Rather than mounting the metadata as a local volume, copy it over, so
that it will be bundled with the image.
Faster access on Windows and shared with collab-server
Remove ports/expose from Hasura and PostgreSQL. Hasura can be accessed
through Nginx, so there was no reason to expose it separately. Postgres
is an internal service that doesn't need to be exposed.
Adds a `docker.yml` workflow that builds and, for tags, publishes docker
images to the GitHub Container Registry.
Heavily baed on Anthony Ledesma's PR (GhostManager#163), this builds the Python
wheels in a separate stage, so that the published docker image does
not have the packages for building or the source codes taking up space.

The Django image has shrunk from roughly 2gb to 400mb.
@ColonelThirtyTwo ColonelThirtyTwo changed the base branch from release/v6.1.0 to master December 11, 2025 19:29
@ColonelThirtyTwo ColonelThirtyTwo dismissed marcpfuller’s stale review December 11, 2025 19:29

The base branch was changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants