Zaj module deploy

# ZajLibrary — operations runbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

## Metadata
- title: Zaj module deploy
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/zaj-module-deploy/
- shelf: Build & Create
- doc_type: operations runbook
- status: current
- kind: runbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: Deploy or update a ZajModules package — autoload dump, config publish, provider check, instant disable rollback. Peeled from MWF2.
- tags: codecanyon, laravel, zajmodules, deployment, modules

## Execution rules (binding)
- Follow `## Steps` in order. Do not skip steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (browser, downloads, OAuth, moving files) need the human — wait for or instruct them; 🤖 **Agent** steps you run in the shell.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, **stop, show what you got, and ask how to proceed** — do not guess or rewrite the procedure.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the step done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this page describes — no refactors, added features, or later-phase work unless the page says so.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.

---

# Zaj module deploy

**Execute from:** [Customizations playbook](/tech-stack/laravel/codecanyon/build/playbooks/customizations/) when adding integration code; this runbook is the deploy card only.

## When

First deploy of a new ZajModule or an update to an existing package under `packages/ZajModules/`.

## Pre-deploy (local)

```bash
grep -r "{Provider}ServiceProvider" bootstrap/providers.php
grep "ZajModules" composer.json   # MUST include Core + category namespace
composer dump-autoload
php artisan tinker --execute="app(\\ZajModules\\{Cat}\\{Mod}\\Services\\{Mod}Service::class);"
open http://<PROJECT>.test/login
```

## New module — deploy sequence

```bash
git add packages/ZajModules/
git commit -m "🔨 🟪 T3 Add-Feature: Add {Module}"
git push origin develop
dep deploy production

ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && composer dump-autoload \
  && php artisan vendor:publish --tag=zajmodules-{module}-config \
  && php artisan config:cache"
```

## Verify

```bash
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan provider:list | grep ZajModules"
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan tinker --execute=\"dump(config('zajmodules.{module}'));\""
```

## Fast disable (no code revert)

```bash
# In shared .env on server
ZAJMODULES_{MODULE}_ENABLED=false
php artisan config:cache
```

## Abort if

ServiceProvider not registered · `.env` vars missing on target server · `packages/workdo/` was touched · module not tested locally with tinker.

## Related

<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />
<LinkCard title="Three-tier admin (handbook)" href="/tech-stack/laravel/codecanyon/learn/handbooks/02-three-tier-admin/" />

# Zaj module deploy

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/zaj-module-deploy/

**Execute from:** [Customizations playbook](/tech-stack/laravel/codecanyon/build/playbooks/customizations/) when adding integration code; this runbook is the deploy card only.

## When

First deploy of a new ZajModule or an update to an existing package under `packages/ZajModules/`.

## Pre-deploy (local)

```bash
grep -r "{Provider}ServiceProvider" bootstrap/providers.php
grep "ZajModules" composer.json   # MUST include Core + category namespace
composer dump-autoload
php artisan tinker --execute="app(\\ZajModules\\{Cat}\\{Mod}\\Services\\{Mod}Service::class);"
open http://<PROJECT>.test/login
```

## New module — deploy sequence

```bash
git add packages/ZajModules/
git commit -m "🔨 🟪 T3 Add-Feature: Add {Module}"
git push origin develop
dep deploy production

ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && composer dump-autoload \
  && php artisan vendor:publish --tag=zajmodules-{module}-config \
  && php artisan config:cache"
```

## Verify

```bash
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan provider:list | grep ZajModules"
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan tinker --execute=\"dump(config('zajmodules.{module}'));\""
```

## Fast disable (no code revert)

```bash
# In shared .env on server
ZAJMODULES_{MODULE}_ENABLED=false
php artisan config:cache
```

## Abort if

ServiceProvider not registered · `.env` vars missing on target server · `packages/workdo/` was touched · module not tested locally with tinker.

## Related

<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />
<LinkCard title="Three-tier admin (handbook)" href="/tech-stack/laravel/codecanyon/learn/handbooks/02-three-tier-admin/" />

Execute from: Customizations playbook when adding integration code; this runbook is the deploy card only.

When

First deploy of a new ZajModule or an update to an existing package under packages/ZajModules/.

Pre-deploy (local)

grep -r "{Provider}ServiceProvider" bootstrap/providers.php
grep "ZajModules" composer.json   # MUST include Core + category namespace
composer dump-autoload
php artisan tinker --execute="app(\\ZajModules\\{Cat}\\{Mod}\\Services\\{Mod}Service::class);"
open http://<PROJECT>.test/login

New module — deploy sequence

git add packages/ZajModules/
git commit -m "🔨 🟪 T3 Add-Feature: Add {Module}"
git push origin develop
dep deploy production

ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && composer dump-autoload \
  && php artisan vendor:publish --tag=zajmodules-{module}-config \
  && php artisan config:cache"

Verify

ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan provider:list | grep ZajModules"
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan tinker --execute=\"dump(config('zajmodules.{module}'));\""

Fast disable (no code revert)

# In shared .env on server
ZAJMODULES_{MODULE}_ENABLED=false
php artisan config:cache

Abort if

ServiceProvider not registered · .env vars missing on target server · packages/workdo/ was touched · module not tested locally with tinker.

Code → test → ship

Three-tier admin (handbook)

# ZajLibrary — operations runbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

## Metadata
- title: Zaj module deploy
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/zaj-module-deploy/
- shelf: Build & Create
- doc_type: operations runbook
- status: current
- kind: runbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: Deploy or update a ZajModules package — autoload dump, config publish, provider check, instant disable rollback. Peeled from MWF2.
- tags: codecanyon, laravel, zajmodules, deployment, modules

## Execution rules (binding)
- Follow `## Steps` in order. Do not skip steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (browser, downloads, OAuth, moving files) need the human — wait for or instruct them; 🤖 **Agent** steps you run in the shell.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, **stop, show what you got, and ask how to proceed** — do not guess or rewrite the procedure.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the step done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this page describes — no refactors, added features, or later-phase work unless the page says so.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.

---

# Zaj module deploy

**Execute from:** [Customizations playbook](/tech-stack/laravel/codecanyon/build/playbooks/customizations/) when adding integration code; this runbook is the deploy card only.

## When

First deploy of a new ZajModule or an update to an existing package under `packages/ZajModules/`.

## Pre-deploy (local)

```bash
grep -r "{Provider}ServiceProvider" bootstrap/providers.php
grep "ZajModules" composer.json   # MUST include Core + category namespace
composer dump-autoload
php artisan tinker --execute="app(\\ZajModules\\{Cat}\\{Mod}\\Services\\{Mod}Service::class);"
open http://<PROJECT>.test/login
```

## New module — deploy sequence

```bash
git add packages/ZajModules/
git commit -m "🔨 🟪 T3 Add-Feature: Add {Module}"
git push origin develop
dep deploy production

ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && composer dump-autoload \
  && php artisan vendor:publish --tag=zajmodules-{module}-config \
  && php artisan config:cache"
```

## Verify

```bash
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan provider:list | grep ZajModules"
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan tinker --execute=\"dump(config('zajmodules.{module}'));\""
```

## Fast disable (no code revert)

```bash
# In shared .env on server
ZAJMODULES_{MODULE}_ENABLED=false
php artisan config:cache
```

## Abort if

ServiceProvider not registered · `.env` vars missing on target server · `packages/workdo/` was touched · module not tested locally with tinker.

## Related

<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />
<LinkCard title="Three-tier admin (handbook)" href="/tech-stack/laravel/codecanyon/learn/handbooks/02-three-tier-admin/" />

# Zaj module deploy

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/zaj-module-deploy/

**Execute from:** [Customizations playbook](/tech-stack/laravel/codecanyon/build/playbooks/customizations/) when adding integration code; this runbook is the deploy card only.

## When

First deploy of a new ZajModule or an update to an existing package under `packages/ZajModules/`.

## Pre-deploy (local)

```bash
grep -r "{Provider}ServiceProvider" bootstrap/providers.php
grep "ZajModules" composer.json   # MUST include Core + category namespace
composer dump-autoload
php artisan tinker --execute="app(\\ZajModules\\{Cat}\\{Mod}\\Services\\{Mod}Service::class);"
open http://<PROJECT>.test/login
```

## New module — deploy sequence

```bash
git add packages/ZajModules/
git commit -m "🔨 🟪 T3 Add-Feature: Add {Module}"
git push origin develop
dep deploy production

ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && composer dump-autoload \
  && php artisan vendor:publish --tag=zajmodules-{module}-config \
  && php artisan config:cache"
```

## Verify

```bash
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan provider:list | grep ZajModules"
ssh <SSH_ALIAS> "cd <DEPLOY_PATH> && php artisan tinker --execute=\"dump(config('zajmodules.{module}'));\""
```

## Fast disable (no code revert)

```bash
# In shared .env on server
ZAJMODULES_{MODULE}_ENABLED=false
php artisan config:cache
```

## Abort if

ServiceProvider not registered · `.env` vars missing on target server · `packages/workdo/` was touched · module not tested locally with tinker.

## Related

<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />
<LinkCard title="Three-tier admin (handbook)" href="/tech-stack/laravel/codecanyon/learn/handbooks/02-three-tier-admin/" />