fimo 0.7.0-experimental.5 → 0.7.0-experimental.6
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.
package/dist/cli/bundle.json
CHANGED
package/dist/cli/index.js
CHANGED
|
@@ -51619,11 +51619,17 @@ whole migration loop; the deterministic CLI does the heavy lifting.
|
|
|
51619
51619
|
env keys, and detects collections and external data sources. Recover
|
|
51620
51620
|
mechanical failures yourself (missing install, pnpm minimumReleaseAge
|
|
51621
51621
|
policy, broken dev script) and re-run it.
|
|
51622
|
-
2. That command REGENERATES this file with the full work order. Re-read it
|
|
51623
|
-
|
|
51624
|
-
|
|
51625
|
-
|
|
51626
|
-
|
|
51622
|
+
2. That command REGENERATES this file with the full work order. Re-read it and
|
|
51623
|
+
continue with the regenerated version.
|
|
51624
|
+
- If it reports a CMS scaffold available (e.g. Strapi detected), ask the user
|
|
51625
|
+
ONE question: bring the CMS content model + example content into Fimo now so
|
|
51626
|
+
the site runs on Fimo? If yes, run \`npx fimo migrate --scaffold-cms\` \u2014 that
|
|
51627
|
+
creates the content types + example content in Fimo AND wires the whole
|
|
51628
|
+
site's reads to Fimo (no manual wiring, no per-view work; unscaffolded types
|
|
51629
|
+
keep reading the CMS). Then \`pnpm dev\` shows the site on Fimo. If they'd
|
|
51630
|
+
rather keep the CMS live, skip it.
|
|
51631
|
+
- For any other DEFAULTED external data source, ask the user, then update
|
|
51632
|
+
\`.fimo/migration/manifest.json\` and re-run \`npx fimo migrate\`.
|
|
51627
51633
|
3. Loop \`npx fimo migrate wrap --check\` after every batch of fixes until it
|
|
51628
51634
|
exits 0 \u2014 that is the only definition of done.
|
|
51629
51635
|
4. Never run \`npx fimo deploy\` or \`fimo publish\` yourself: report the
|
package/package.json
CHANGED