Skip to content

Point developers to devcontainer-reset-db in README - #60

Merged
kurowski merged 3 commits into
mainfrom
readme-reset-db
Aug 21, 2026
Merged

Point developers to devcontainer-reset-db in README#60
kurowski merged 3 commits into
mainfrom
readme-reset-db

Conversation

@kurowski

Copy link
Copy Markdown
Member

Summary

Updates the Tips and tricks section to lead with uceap devcontainer-reset-db instead of uceap refresh-content.

  • Lead recommendation is now devcontainer-reset-db: it recreates the mariadb container from the seed data baked into its image and runs drush deploy, with no Pantheon download.
  • The update-hook / config-change recipe uses devcontainer-reset-db, with composer install added before it — unlike refresh-content, reset-db doesn't install dependencies, and its trailing drush deploy runs against whatever code is checked out.
  • Added a paragraph on when refresh-content is still the right tool: the baked seed data is a point-in-time DEV snapshot and excludes web/sites/default/files.
  • Kept the TERMINUS_ENV=live uceap refresh-content tip unchanged — reset-db can't pull LIVE data.

🤖 Generated with Claude Code

kurowski and others added 3 commits August 21, 2026 13:29
Recommend `uceap devcontainer-reset-db` as the default way to reset a
local database, and clarify when `uceap refresh-content` is still needed
(current DEV content, the files directory, or LIVE data).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
devcontainer-reset-db runs drush deploy by default, so the recipe needs
--skip-deploy to leave the database at its seed state and let the
developer run the composer install / drush deploy dance themselves.

The qa checkout is dropped: the seed database is already at the deployed
state, so switching branches before the reset accomplishes nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@kurowski
kurowski merged commit b718324 into main Aug 21, 2026
1 check passed
@kurowski
kurowski deleted the readme-reset-db branch August 21, 2026 13:34
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.

1 participant