Skip to content
prod 352bb92
Browse

Tagged: codecanyon

All Tags
codecanyon
154 pages
5 related

Pages with this tag

Customization decision

145

The one-screen routing for any change to a CodeCanyon Laravel app — vendor file edit → vendor-customizations overlay, new functionality → ZajModule, vendor-table column → additive _zaj migration — so nothing is lost on the next vendor update.

Gotchas

146

The CodeCanyon Laravel traps that bite — per-environment APP_KEY, APP_DEBUG off the box, the utf8mb4 schema, the vendor overlay that composer install reverts, secrets in server sync, and Cloudflare Full (Strict) SSL — each with the one-line fix.

CodeCanyon AI System kit

147

A standalone copy-paste kit that stands up the Phase 1 AI System for a fresh CodeCanyon Laravel app — constitution, Claude config + permission modes + safety hooks, universal rules, and other-IDE wiring.

Laravel/CodeCanyon — Kits

148

Reusable, copy-paste bundles for CodeCanyon Laravel work — like the vendor-customization restore script that re-applies your overlay after composer install.

Vendor-customization restore kit

149

The restore-vendor-customizations.php script — re-applies your resources/vendor-customizations/ overlay after composer install or a vendor update reverts vendor/ to vanilla, honoring your ZAJ:BEGIN/END markers.

Laravel/CodeCanyon — Templates

150

Copy-and-fill starter files for CodeCanyon Laravel deployment — deployer, environment, web server, and git ignore.

Deployer — deploy.php

151

The zero-downtime Deployer config for a CodeCanyon Laravel app — project block to fill in, smoke test, health check, and rollback baked in.

Environments — .env templates

152

Three Laravel .env templates — local, staging, production — with the keys that change between stages and a per-env safety checklist.

Web server & git

153

Root + public .htaccess for an Apache-hosted CodeCanyon Laravel app — routing, HTTPS, security headers, caching — plus a CodeCanyon-ready .gitignore.

Use local ZajLibrary MCP

154

Run zajlibrary-local on port 4321 — when to prefer local over prod, dev setup, index refresh, CodeCanyon playbook QA, and testing submit_feedback on the dev queue.