Tagged: git
Pages with this tag
Repository & version setup
1ZIP extract, Git init, vendor T1 commit, author branch/tag, semver, and changelog — gates before local dev.
Phase 2 · Code & repository setup
2Extract the CodeCanyon vendor ZIP cleanly, initialize git with a frozen vendor snapshot and branch strategy, and wire .env templates — so every later vendor update diffs cleanly.
1 · Prerequisites
3Collect everything the operator must provide, ensure every CLI tool a later phase needs is installed, then create the private GitHub repo, hosting sites, and databases — and wire passwordless SSH to both servers — before anything depends on them.
2 · Branch strategy
4Choose Option A (solo/small team — one setup branch, one commit per phase) or Option B (a branch per phase, merged via PR), then learn the branch model the rest of the playbook commits against.
4 · Initialize the repository
5Set session variables, write .gitignore BEFORE git init so secrets, installed dependencies, the installer-complete marker, and per-env symlinks never enter history, then initialize git on develop and lock down per-directory storage ignores.
6 · Commit & freeze the vendor
6Verify the pristine vendor baseline from AI dev environment setup, push develop + author/vX + tag to the private remote, cut your working branch, and prove the seam is clean — without recreating the vendor import.
6 · Commit & secure
7Commit the repo-safe installer artifacts, document any author patches in the shipped vendor tree, verify deploy symlinks and shared_files, then lock down /install and /update with layered defense.
7 · ServerSync capture
8Run the first live ServerSync capture after the selected non-production deploy — verify workflow availability and version parity, re-audit clear_paths ↔ GIT_ONLY_PATHS, trigger the run, and review the resulting PR file-by-file.
1 · Static audit — code, dependencies, git
9Fast, deterministic checks that need no browser — project structure, Composer security audit, git hygiene, code-quality/secrets scan — plus migration analysis and FVDUT storage classification.
3 · Harden, verify & sync (P3–P7)
10Lock down installer-friendly permissions, verify schema parity against staging, review ServerSync, prove production mail flow, then sync all branches back to a shared base and tag the release as your rollback and audit anchor.
Server sync capture
11Reverse-git — capture admin uploads, installer output, and server-side files back into develop before the next deploy wipes them. Peeled from MWF3.
Version control & git workflow
12How small commits, a vendor-safe branch model, and a reverse-capture loop keep a CodeCanyon Laravel project recoverable and upgrade-safe.