Tagged: codecanyon
Pages with this tag
7 · Release + incident response
49Close the phase — bootstrap or update the changelog and version, tag the release, then stand up an incident-response runbook (Sentry, uptime, SSL expiry, severities, contacts) wired into the repo as dev-only.
Phase 5 · Staging deploy
50Take the app from "runs locally" to "runs on a real non-production server" — provision the selected target, point DNS, ship the first atomic release, run the web installer, verify the schema, prove rollback, and open any standing observation follow-up.
1 · Pre-flight & provision host
51Consume the Phase 4 handoff, pin Composer to the confirmed deploy PHP, run the canonical pre-flight, prepare and push the selected non-production branch, then scaffold the server — deploy tree, .user.ini limits, and the shared .env with APP_KEY left empty.
2 · DNS + SSL
52Confirm the non-production domain resolves to the server and serves a valid TLS chain before the first release lands — a deploy onto an unresolved or untrusted host wastes a round-trip.
3 · First release
53Run the atomic first deploy, confirm APP_KEY and clear caches with the versioned PHP binary, verify the Deployer directory tree and the .env symlink (a 5-second check that prevents a 90-minute outage), confirm demo content, then loosen permissions for the installer.
4 · Installer + harden
54Temporarily unblock /install, run the CodeCanyon web installer wizard, verify the app loads, then immediately re-block /install + /update and re-harden storage and .env permissions from the installer's insecure 777 state.
5 · Schedule, migrations + schema
55Install and verify the every-minute schedule:run cron with the provider path that fits the selected host, then verify migrations and export + diff the selected non-production schema against your local baseline.
6 · Rollback + monitor
56Prove a one-command rollback restores a previous release, run the immediate post-deploy sweeps, and open the standing 24–48h observation follow-up without leaving Phase 5 falsely partial.
7 · ServerSync capture
57Run 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.
8 · Deep codebase audit
58A non-production deep audit of the codebase — project structure, composer security audit, Git hygiene, FVDUT storage persistence, secret + debug-code scans (with the word-boundary fix for dd()), storage-tracked-file triage, CodeCanyon frontend anti-patterns, and an optional schema audit.
9 · Atlas Cloud
59Decide whether to register your schema with Atlas Cloud for versioned migration tracking — open the SSH tunnel, build a baseline migration from the selected non-production schema, push it to Atlas Cloud, apply the baseline to that target, and wire up GitHub CI. Requires an active Atlas Cloud license; free alternatives noted.
Phase 6 · SuperAdmin setup
60Log in as the superadmin and configure everything the vendor exposes in the admin panel — branding, theme, email, payments, plans, legal pages, and analytics — using a check-first pattern that adapts to any CodeCanyon app.