Repository navigation
ci: deploy the website to S3 and CloudFront - #227
Open
davecramer wants to merge 1 commit into
Open
davecramer wants to merge 1 commit into
davecramer wants to merge 1 commit into
Conversation
davecramer
force-pushed
the
ci-deploy-site-s3
branch
from
October 27, 2026 18:19
5b26d61 to
47584b5
Compare
docs.yml builds the site from psqlodbc-www on git.postgresql.org with its docs/ directory replaced by docs/ from this repository, and uploads it as the site artifact. It runs on pull requests that change docs/ or the two workflows, and lints the workflows there with actionlint. docs-deploy.yml calls docs.yml and, on main, uploads the site to the S3 bucket under a new prefix and points the CloudFront KeyValueStore key at that prefix, so a rollback sets the key back to an earlier deploy. A run on another branch builds the site and stops there. The bucket, role and KeyValueStore come from repository variables, which the comment at the top of docs-deploy.yml lists. This follows the pgjdbc site deploy. Assisted-By: Claude
davecramer
force-pushed
the
ci-deploy-site-s3
branch
from
October 27, 2026 19:19
47584b5 to
f15cfcc
Compare
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.
Builds https://odbc.postgresql.org/ in GitHub Actions and deploys it to S3 and CloudFront, following the pgjdbc site deploy.
This branch is on top of #226, which registers
docs-deploy.ymlonmainso that the deploy can be started from this branch before it is merged. Merge #226 first; this PR then replaces its placeholder.Workflows
docs.ymlbuilds the site from psqlodbc-www with itsdocs/directory replaced bydocs/from this repository. That is the copy the psqlodbc-www README asks for. It uploads the result as thesiteartifact. It runs on pull requests that changedocs/or either workflow, and lints both workflows there with actionlint.docs-deploy.ymlcallsdocs.ymland, onmainonly, uploads the site tos3://<bucket>/site/<branch>/<yyyymmddThhmmssZ>-<commit>/. It then sets the CloudFront KeyValueStore key to<branch>/<yyyymmddThhmmssZ>-<commit>. Earlier deploys stay in the bucket, so a rollback sets the key back to an earlier value. A run on another branch builds the site and stops there.Start a deploy with:
Needed before the first deploy
None of this is created by this PR:
SITE_AWS_ROLE_ARN,SITE_AWS_REGION,SITE_S3_BUCKET,SITE_CLOUDFRONT_KVS_ARNandSITE_CLOUDFRONT_KVS_KEY, described at the top ofdocs-deploy.yml.site/in front of the key value./backups/psqlodbc-cvs.tar.bz2, which the current site serves but neither repository contains, served from outsidesite/.Testing
I ran the build step locally. Its output has the psqlodbc-www pages,
media/andREADME.txt, withdocs/from this repository. The deploy job has not been run, because the AWS resources above don't exist yet.