You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once we're happy that the editing deployment is consuming data properly
Switch web pods to use the readonly postgres DB replicas and GCS storage bucket
Initially, add DATABASE_URL and MEDIA_URL via secrets
GRANT pg_read_all_data TO <BEDROCK READONLY USER NAME>;
once stable, move MEDIA_URL to env vars and out of secrets
Disable script to download new sqlite DB from the bucket if postgres is in play (this is now redundant for Dev/Stage/Prod, but still relevant to Bedrock-test and Demos)
Add tooling to allow devs to download a sqlite version of the PG database
The content you are editing has changed. Please copy your edits and refresh the page.
Wagtail in Bedrock
This epic outlines the work needed to integrate Wagtail into Bedrock in a way that's compliant with our RRA and generally effective.
## Necessary tasks
These will be split out into individual Issues as we prep them
Move fromDecision: stick with django-jinja, because its feature set is betterdjango_jinja
to core Django Jinja2 support - this will make it easer to integrate Wagtailwagtail-localize
Refactor legacy, custom i18n mechanism to use core django i18n #14256Add a simple migration to change text content of the root page, to avoid user confusion Issue hereDisable rendition generation if doesn't exist already - catch the request early in middleware on the web deploymentinvalid concernREDIS_URL
to Editing Deployment, not Web DeploymentContent management and access planning(Will move to own Epic)Rollout plan
Use an SSH tunnel to connect to the relevant postgres DB as the appropriate user and run the pre-fill-postgres script
Stand up Editing deployment, connected to postgres
Set MEDIA_URL in infra and also align with the CDN Add helper to get only the hostname out of MEDIA_URL #14723
CMS mode tuning:
Add new command to keep the editing deployment's DB up to date #14715
Once we're happy that the editing deployment is consuming data properly
DATABASE_URL
andMEDIA_URL
via secretsGRANT pg_read_all_data TO <BEDROCK READONLY USER NAME>;
MEDIA_URL
to env vars and out of secretsAdd tooling to allow devs to download a sqlite version of the PG database
Final push tasks (ordered in priority terms)
Post-MVP CMS tasks
The text was updated successfully, but these errors were encountered: