Feat: define postgres, pgweb Compose services - #3496
Merged
Conversation
Contributor
|
Preview url: https://benefits-3496--cal-itp-previews.netlify.app |
Contributor
thekaveman
force-pushed
the
feat/postgres-service
branch
from
February 13, 2026 22:28
d08456d to
d43d5af
Compare
thekaveman
marked this pull request as ready for review
February 13, 2026 22:29
5 tasks
5 tasks
lalver1
approved these changes
Feb 17, 2026
lalver1
left a comment
Member
There was a problem hiding this comment.
Looks good to me! And works fine locally too 👍
I agree about the Postgres image, we can revisit this once we start working on the infrastructure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is some very initial work I thought we could use to get started on #3446.
Here we define a
postgresservice in the Compose file for a local PostgreSQL database server, and an associatedpgwebservice for interacting with the server. No other integration with the devcontainer or Django is attempted in this PR.Required environment variables with default values were also added to the
.env.sampleand relevant docs are updated.NOTE: I went with
postgres:16which is not the latest image, to match the config we used in CDRC. At the time, this was the latest available in Azure's managed PostgreSQL offering, and we can easily revisit when we start configuring the cloud services.Testing this PR
.envfile with the new variables, leaving the defaultsdocker compose up -d pgwebhttp://localhost:8081pgwebinterface connected to an (empty)postgresdatabase: