@spree/docs 0.1.83 → 0.1.84
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -78,10 +78,11 @@ Which command after which change:
|
|
|
78
78
|
| What changed | What to run |
|
|
79
79
|
|---|---|
|
|
80
80
|
| Ruby code in `spree/*` gems | Nothing — gems are bind-mounted; code reloads on the next request |
|
|
81
|
-
| A new migration in a gem | `cd server && pnpm exec spree migrate` |
|
|
82
|
-
| Gem dependencies (gemspec / Gemfile) | `cd server && pnpm exec spree bundle install`
|
|
81
|
+
| A new migration in a gem | Nothing — the next `pnpm server:dev` boot applies it (or `cd server && pnpm exec spree migrate` while the stack runs) |
|
|
82
|
+
| Gem dependencies (gemspec / Gemfile / lock drift after `git pull`) | Nothing — the next `pnpm server:dev` boot self-heals via `bundle check || bundle install` (or `cd server && pnpm exec spree bundle install` while the stack runs) |
|
|
83
83
|
| Compose files / `server/.env` | `pnpm server:dev` (force-recreates the containers) |
|
|
84
|
-
| `server/Dockerfile` / `.ruby-version` | `pnpm server:build`, then `pnpm server:dev` |
|
|
84
|
+
| `server/Dockerfile` / `.ruby-version` / starter update that breaks the image build ("lockfile can't be updated because frozen") | `pnpm server:build`, then `pnpm server:dev` — the build script handles the edge-rewritten `Gemfile.lock` automatically |
|
|
85
|
+
| Meilisearch image bump ("database version … is incompatible") | Remove the `server_meilisearch_data` volume, boot, then reindex (`pnpm exec spree rake spree:search:reindex`) — the index is derived data |
|
|
85
86
|
| Broken beyond repair | `pnpm server:setup` (full reset — wipes the database and volumes) |
|
|
86
87
|
|
|
87
88
|
Re-run `pnpm server:setup` **only** to fully reset — it does `docker compose down -v` + `rm -rf ./server`, wiping all DB data.
|