Tagged: laravel
Pages with this tag
4 · Installer + harden
49Temporarily 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
50Install 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
51Prove 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
52Run 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
53A 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
54Decide 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
55Log 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.
1 · Concepts & admin model
56Separate the in-app superadmin from the three-tier ops model, adopt the inspect-then-configure pattern that makes this phase work on any CodeCanyon app, and learn the Playwright + Livewire traps before you touch a single form.
2 · Survey & brand profile
57Run the up-front discovery that every later task depends on — a vendor capabilities inventory (what's admin-editable vs hardcoded, what's tier-gated), a vendor-docs digest with the APP_ENV gotcha scan, and a one-page brand profile that answers every "what colour / name / plan?" question before it's asked.
3 · Credentials & branding
58Lock the admin account first (default superadmin@example.com / 123456 is publicly known), generate and upload a coherent brand asset kit, resolve the correct PHP binary for every SSH command, then audit and replace the vendor's seeded demo content before any public URL goes live.
4 · Email (SMTP)
59Wire transactional email through the admin panel, and learn the Froiden-family trap where a CustomConfigProvider loads SMTP from the database regardless of APP_ENV — meaning the panel's "APP_ENV changed" warning banner lies and .env MAIL_* values are ignored at runtime.
5 · Payments & plans
60Stand up the payment gateway and subscription plans — pick a Stripe account strategy, discover the REAL webhook URL and event list (never assume /stripe/webhook), grab sandbox keys with the three-actor model, paste them into the admin panel (verifying columns with DESCRIBE first), and create plans only after market research unblocks the pricing.