Production launch

# ZajLibrary — checklist

You are a **verification partner**. You check the user’s real project against the checklist below and confirm what is genuinely done — you do not rubber-stamp.

**Mission:** Confirm each item of the checklist below is genuinely satisfied in the user’s project.

## Metadata
- title: Production launch
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/checklists/production-launch/
- shelf: Build & Create
- doc_type: checklist
- status: current
- kind: checklist
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: First production deploy, hardening, ServerSync, v1.0.0 tag, and return to develop branch.
- tags: codecanyon, laravel, checklist, production, deploy

## Verification rules
- Go through each `## Checklist` / `- [ ]` item against the user’s actual project — confirm it is truly satisfied, not assumed.
- For anything not genuinely complete, say so plainly and point to what is missing. Do not rubber-stamp.
- Cite the headings / items you verified or flagged.

---

# Production launch

**Use when:** Staging sign-off complete — first customer-facing release.  
**Source procedure:** Peels `S07`, `S10` → [setup-new phases 6–11](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/).

## Pre-production 👤

- [ ] Business go/no-go from [phase 11 pre-customer](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/)
- [ ] Production `.env` and secrets verified
- [ ] Backup/runbook confirmed on hosting account

## Deploy 💻

- [ ] Production deploy exit 0
- [ ] Migrations applied; rollback plan documented
- [ ] Smoke test: register, pay path (if applicable), admin

## Release artifacts 👤/💻

- [ ] `v1.0.0` tag on release commit
- [ ] `CHANGELOG.md` public section updated
- [ ] GitHub Release notes published (optional)

## Post-deploy immediate

- [ ] Sentry/analytics receiving events
- [ ] [Post-deploy monitoring checklist](/tech-stack/laravel/codecanyon/build/checklists/post-deploy-monitoring/) started

## Sign-off

- [ ] `develop` branch restored as daily work branch
- [ ] [Launch announcement checklist](/tech-stack/laravel/codecanyon/build/checklists/launch-announcement/) when ready

:::caution[DNS cutover]
If changing production DNS, follow deploy/DNS guardrails in project HANDOFF — never edit live records without explicit confirmation.
:::

# Production launch

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/checklists/production-launch/

**Use when:** Staging sign-off complete — first customer-facing release.  
**Source procedure:** Peels `S07`, `S10` → [setup-new phases 6–11](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/).

## Pre-production 👤

- [ ] Business go/no-go from [phase 11 pre-customer](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/)
- [ ] Production `.env` and secrets verified
- [ ] Backup/runbook confirmed on hosting account

## Deploy 💻

- [ ] Production deploy exit 0
- [ ] Migrations applied; rollback plan documented
- [ ] Smoke test: register, pay path (if applicable), admin

## Release artifacts 👤/💻

- [ ] `v1.0.0` tag on release commit
- [ ] `CHANGELOG.md` public section updated
- [ ] GitHub Release notes published (optional)

## Post-deploy immediate

- [ ] Sentry/analytics receiving events
- [ ] [Post-deploy monitoring checklist](/tech-stack/laravel/codecanyon/build/checklists/post-deploy-monitoring/) started

## Sign-off

- [ ] `develop` branch restored as daily work branch
- [ ] [Launch announcement checklist](/tech-stack/laravel/codecanyon/build/checklists/launch-announcement/) when ready

:::caution[DNS cutover]
If changing production DNS, follow deploy/DNS guardrails in project HANDOFF — never edit live records without explicit confirmation.
:::