Tagged: codecanyon
Pages with this tag
4 · Run the installer
37Raise the PHP-FPM and nginx timeouts so big migration runs don't 504, pre-flight four preconditions, complete the installer, then capture every seeded/default credential safely.
5 · Verify migrations & schema
38Confirm every migration ran (modules included), troubleshoot pending ones the right way, capture a normalized schema baseline for cross-environment diffs, then run the 11-point gate that proves the app actually works.
6 · Commit & secure
39Commit 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 · Shared-hosting readiness
40Verify that the hosting account has the Admin-Server toolkit before the deploy pipeline starts, or run the shared-hosting playbook first.
8 · Dev tooling
41Decide which local-development power-ups to adopt — Atlas schema management, a database GUI (Bytebase), Redis caching via Herd Pro, and a right-sized debug-tools stack. None block launch; each has a free fallback.
Phase 4 · Deploy pipeline
42Stand up everything that makes deployment possible — Deployer for zero-downtime releases, environment domains + SSL, production .env templates, and (recommended) CI, DNS email records, and a CDN — so Phase 5 can run the first observed non-production deploy.
1 · Deployer (zero-downtime)
43Install Deployer and author deploy.php for atomic releases — symlinked current → timestamped releases, shared storage and .env, retention, hooks, server binary paths, and an SSH-verified dry run.
2 · Environment domains + SSL
44Plan the environment hostname map, add A/CNAME records, provision SSL/TLS certificates, force HTTP→HTTPS, and confirm everything with a five-check CLI verification (dig, HEAD, redirect, proxy, cert details).
3 · Production .env
45Assemble a safe production env source — bidirectional drift check against .env.example, a Git-history secret scan, production flags, and a secrets-manager render check. Server upload and runtime verification happen in Phase 5 or Phase 12.
4 · CI + ServerSync
46Wire GitHub Actions for deploys and ServerSync — author the workflows, set the GitHub Secrets (PAT, SSH key), keep clear_paths ↔ GIT_ONLY_PATHS symmetric, and validate with actionlint. First live runs happen in Phase 5 or Phase 12.
5 · DNS email records
47Make transactional email deliverable — verify the email provider, add SPF, DKIM, and DMARC records (plus MX), interpret CAA safely, and confirm everything with dig.
6 · Cloudflare CDN
48Front the app with Cloudflare on the Free plan — nameserver cutover, API-driven DNS, Full (Strict) SSL + HSTS, WAF and rate limiting, cache rules, DNSSEC, and a final API verification probe. Rocket Loader stays OFF for Laravel.