Complete monorepo flattening #1956

Activity

1. bpamiri

   added

   enhancement

   on Mar 15, 2026
2. bpamiri

   added a commit that references this issue on Mar 15, 2026

   Remove stale planning/analysis markdown files from repo root

   ...

   be4912a
3. bpamiri commented on Mar 16, 2026

   

   bpamiri

   on Mar 16, 2026

   CollaboratorAuthor

   More actions

   Analysis

   Synopsis

   Finalize the monorepo flattening so the repo works with a single git clone + box server start — unifying paths, Docker mounts, and test directories.

   Merit Assessment

   Recommendation: Proceed with modifications

   • The flattening is already largely done: app/, config/, public/, vendor/, tests/ all exist at root. lucee.json has correct mappings. The build scripts (prepare-base.sh, prepare-core.sh) already copy from root-level dirs.
   • One real remaining issue: release.yml line 78 still reads templates/base/src/box.json which no longer exists (templates/base/src/ is gone). This will fail on main branch releases.
   • Docker compose volume mounts already point at ./ (e.g., ./:/wheels-test-suite). Per-engine config overrides use tools/docker/<engine>/ paths which are correct.
   • The templates/base/ directory still exists but only as a build template source — this is by design, not a leftover.

   Implementation Plan

   1. Fix release.yml line 78 — change jq -r '.version' templates/base/src/box.json to jq -r '.version' box.json (the version validation step in the "Validate Release Checklist" block). This is the only actual bug.
   2. Verify zero-config startup — run box server start from repo root with lucee.json and confirm the app loads. The mappings in lucee.json (/wheels -> ../vendor/wheels, /app -> ../app, etc.) assume webroot is public/, which is configured.
   3. Audit for any other stale templates/base/src references — grep found one in .github/workflows/tests.yml.keep (a backup file, can be deleted) and the release.yml bug above.
   4. Complexity: Low — 1-2 file edits + verification.

   Dependencies & Risks

   • The release.yml fix is a silent bug that will surface on the next main branch release. Should be fixed before any stable release.
   • Related: Update GitHub Actions workflows for flattened repo #1957 covers additional workflow path updates and should be addressed together.
   • No breaking change risk — this is cleanup/bugfix only.

   ---

   Automated analysis by @claude — review and adjust as needed.

   👀React with 👀1Reacted by claude
4. bpamiri

   added

   phase:1-stabilizeBugs, cleanup, CI fixes — tackle firstBugs, cleanup, CI fixes — tackle first

   on Mar 16, 2026
5. bpamiri

   added a commit that references this issue on Mar 16, 2026

   Remove stale templates/ directory and legacy workflow file

   ...

   This issue will close once commit 82ab9d2 is merged into the 'develop' branch.

   82ab9d2
6. bpamiri

   added this to the v3.1 milestone on Mar 17, 2026
7. bpamiri

   closed this as completedin #1988on Mar 17, 2026