Tagged: codecanyon
Pages with this tag
Phase 2 · Code & repository setup
25Extract 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
26Collect 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
27Choose 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.
3 · Extract & snapshot the vendor
28Extract the CodeCanyon ZIP into a verified Laravel root, capture vendor docs, back up a pristine copy, then inspect and classify any author edits inside vendor/ — preserving real patches, stripping license-injection backdoors, and proving a clean tree boots — before a single feature is touched.
4 · Initialize the repository
29Set 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.
5 · Wire .env templates
30Back up the vendor's env into the project vault, lay down local/staging/production templates, activate local and generate the app key, then verify the per-environment values that differ.
6 · Commit & freeze the vendor
31Verify 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.
7 · Project standards (recommended)
32Project-structure scaffolding (Admin-Local vault + docs), commit & documentation standards with the Zaj customization strategy, and version management (SemVer + Zaj-CHANGELOG) — SHOULD, not skip-by-default.
Phase 3 · Local development
33Install dependencies, build assets locally, run the CodeCanyon installer, and get the app booting at a local HTTPS domain with login working — the first time you see it run.
1 · Dependencies & assets
34Authenticate Composer to dodge the rate limit, install PHP and JS dependencies without clobbering vendor patches, audit .env.example for fail-loud placeholders, then build and commit frontend assets.
2 · Local database
35Confirm the Phase 2 local MySQL/MariaDB database is running, utf8mb4, and wired through .env so the installer can connect.
3 · Storage, symlinks & SSL
36Create the storage symlink, detect and wire your app's addon system (Modules vs packages vs addons), then link the project to Herd over HTTPS and prove the installer route is reachable.