Server sync capture

# 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: Server sync capture
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/server-sync-capture/
- shelf: Build & Create
- doc_type: operations runbook
- status: current
- kind: runbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: Reverse-git — capture admin uploads, installer output, and server-side files back into develop before the next deploy wipes them. Peeled from MWF3.
- tags: codecanyon, laravel, server-sync, git, security

## 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.

---

# Server sync capture

**Execute from:** [2 · Server sync](/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/) (WF-SYNC playbook step). This runbook is the command card.

## When

Changes happened **on the server** (admin uploads, installer, manual SSH edit) and must land in git **before** the next deploy.

```mermaid
flowchart LR
  S["Server writes files"] --> C["Capture commit<br/>on production/develop"]
  C --> R["👤 Review list<br/>no secrets"]
  R --> D["Merge to develop"]
  D --> M["Continue MWF1 ship"]
```

## Capture (manual SSH)

```bash
ssh <SSH_ALIAS>
cd <DEPLOY_PATH>
git status                    # 👤 Review — no .env, vendor/, logs
git add storage/app public/images   # example paths only
git commit -m "🔄 ⬛ T5 ServerSync-Upload: Capture <description>"
git push origin develop

# Local
git checkout develop && git pull origin develop
```

## Preferred

Trigger the repo **capture-production** GitHub Action (Actions → workflow dispatch) when configured — same review gate applies.

## Never stage

`.env` · `vendor/` · `node_modules/` · `storage/logs/` · `storage/sessions/` · `*.key` · `*.pem`

## Rollback bad sync

```bash
git log --oneline -5
git revert <sync-commit-hash>
git push origin develop
```

## Related

<LinkCard title="Server sync playbook step" href="/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/" />
<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />

# Server sync capture

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/server-sync-capture/

**Execute from:** [2 · Server sync](/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/) (WF-SYNC playbook step). This runbook is the command card.

## When

Changes happened **on the server** (admin uploads, installer, manual SSH edit) and must land in git **before** the next deploy.

```mermaid
flowchart LR
  S["Server writes files"] --> C["Capture commit<br/>on production/develop"]
  C --> R["👤 Review list<br/>no secrets"]
  R --> D["Merge to develop"]
  D --> M["Continue MWF1 ship"]
```

## Capture (manual SSH)

```bash
ssh <SSH_ALIAS>
cd <DEPLOY_PATH>
git status                    # 👤 Review — no .env, vendor/, logs
git add storage/app public/images   # example paths only
git commit -m "🔄 ⬛ T5 ServerSync-Upload: Capture <description>"
git push origin develop

# Local
git checkout develop && git pull origin develop
```

## Preferred

Trigger the repo **capture-production** GitHub Action (Actions → workflow dispatch) when configured — same review gate applies.

## Never stage

`.env` · `vendor/` · `node_modules/` · `storage/logs/` · `storage/sessions/` · `*.key` · `*.pem`

## Rollback bad sync

```bash
git log --oneline -5
git revert <sync-commit-hash>
git push origin develop
```

## Related

<LinkCard title="Server sync playbook step" href="/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/" />
<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />

Execute from: 2 · Server sync (WF-SYNC playbook step). This runbook is the command card.

When

Changes happened on the server (admin uploads, installer, manual SSH edit) and must land in git before the next deploy.

flowchart LR
  S["Server writes files"] --> C["Capture commit<br/>on production/develop"]
  C --> R["👤 Review list<br/>no secrets"]
  R --> D["Merge to develop"]
  D --> M["Continue MWF1 ship"]

Capture (manual SSH)

ssh <SSH_ALIAS>
cd <DEPLOY_PATH>
git status                    # 👤 Review — no .env, vendor/, logs
git add storage/app public/images   # example paths only
git commit -m "🔄 ⬛ T5 ServerSync-Upload: Capture <description>"
git push origin develop

# Local
git checkout develop && git pull origin develop

Preferred

Trigger the repo capture-production GitHub Action (Actions → workflow dispatch) when configured — same review gate applies.

Never stage

.env · vendor/ · node_modules/ · storage/logs/ · storage/sessions/ · *.key · *.pem

Rollback bad sync

git log --oneline -5
git revert <sync-commit-hash>
git push origin develop

Server sync playbook step

Code → test → ship

# 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: Server sync capture
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/server-sync-capture/
- shelf: Build & Create
- doc_type: operations runbook
- status: current
- kind: runbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: Reverse-git — capture admin uploads, installer output, and server-side files back into develop before the next deploy wipes them. Peeled from MWF3.
- tags: codecanyon, laravel, server-sync, git, security

## 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.

---

# Server sync capture

**Execute from:** [2 · Server sync](/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/) (WF-SYNC playbook step). This runbook is the command card.

## When

Changes happened **on the server** (admin uploads, installer, manual SSH edit) and must land in git **before** the next deploy.

```mermaid
flowchart LR
  S["Server writes files"] --> C["Capture commit<br/>on production/develop"]
  C --> R["👤 Review list<br/>no secrets"]
  R --> D["Merge to develop"]
  D --> M["Continue MWF1 ship"]
```

## Capture (manual SSH)

```bash
ssh <SSH_ALIAS>
cd <DEPLOY_PATH>
git status                    # 👤 Review — no .env, vendor/, logs
git add storage/app public/images   # example paths only
git commit -m "🔄 ⬛ T5 ServerSync-Upload: Capture <description>"
git push origin develop

# Local
git checkout develop && git pull origin develop
```

## Preferred

Trigger the repo **capture-production** GitHub Action (Actions → workflow dispatch) when configured — same review gate applies.

## Never stage

`.env` · `vendor/` · `node_modules/` · `storage/logs/` · `storage/sessions/` · `*.key` · `*.pem`

## Rollback bad sync

```bash
git log --oneline -5
git revert <sync-commit-hash>
git push origin develop
```

## Related

<LinkCard title="Server sync playbook step" href="/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/" />
<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />

# Server sync capture

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/runbooks/server-sync-capture/

**Execute from:** [2 · Server sync](/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/) (WF-SYNC playbook step). This runbook is the command card.

## When

Changes happened **on the server** (admin uploads, installer, manual SSH edit) and must land in git **before** the next deploy.

```mermaid
flowchart LR
  S["Server writes files"] --> C["Capture commit<br/>on production/develop"]
  C --> R["👤 Review list<br/>no secrets"]
  R --> D["Merge to develop"]
  D --> M["Continue MWF1 ship"]
```

## Capture (manual SSH)

```bash
ssh <SSH_ALIAS>
cd <DEPLOY_PATH>
git status                    # 👤 Review — no .env, vendor/, logs
git add storage/app public/images   # example paths only
git commit -m "🔄 ⬛ T5 ServerSync-Upload: Capture <description>"
git push origin develop

# Local
git checkout develop && git pull origin develop
```

## Preferred

Trigger the repo **capture-production** GitHub Action (Actions → workflow dispatch) when configured — same review gate applies.

## Never stage

`.env` · `vendor/` · `node_modules/` · `storage/logs/` · `storage/sessions/` · `*.key` · `*.pem`

## Rollback bad sync

```bash
git log --oneline -5
git revert <sync-commit-hash>
git push origin develop
```

## Related

<LinkCard title="Server sync playbook step" href="/tech-stack/laravel/codecanyon/build/playbooks/continuous-deploy/02-server-sync/" />
<LinkCard title="Code → test → ship" href="/tech-stack/laravel/codecanyon/build/runbooks/code-test-ship/" />