# Capture changes into my fork

You're integrating one or more commits from a sibling GitHub fork into
the CURRENT WORKING DIRECTORY. The CWD should already be a clean git
working tree on a branch you're willing to commit to.

## Source thread: Lef-F cuts Mike loose from the cloud

A complete self-hosted stack so a firm can run Mike on its own infrastructure with a single command.

| # | SHA | Subject | Fork | Authored |
|---|-----|---------|------|----------|
| 1 | [`4038fe74`](https://github.com/Lef-F/mike/commit/4038fe74d1b95ff509117cfe0ec17ab54b008aa2) | docs: add self-host docker-compose spec and plan | `Lef-F/mike` | 2026-05-04 |
| 2 | [`2a9edade`](https://github.com/Lef-F/mike/commit/2a9edadef963a43d971a48c784fd4eb820fc6178) | feat: add generate-secrets.sh for docker-compose self-host stack | `Lef-F/mike` | 2026-05-04 |
| 3 | [`6fe97e23`](https://github.com/Lef-F/mike/commit/6fe97e23266240e3b6c7022bdd8375a1bd96b7c6) | fix: harden generate-secrets.sh permissions, openssl guard, CRLF | `Lef-F/mike` | 2026-05-04 |
| 4 | [`c027e2e6`](https://github.com/Lef-F/mike/commit/c027e2e6ccd4e2aec8af63e35494f0b1858b20aa) | feat: add root .env.example for docker-compose stack | `Lef-F/mike` | 2026-05-04 |
| 5 | [`93152400`](https://github.com/Lef-F/mike/commit/9315240017701bacc924ac9489c1603d03cdca07) | feat: add postgres init script for PostgREST roles and auth helpers | `Lef-F/mike` | 2026-05-04 |
| 6 | [`ff85a408`](https://github.com/Lef-F/mike/commit/ff85a40894a4dd340afc3001360c1b554cfe441a) | feat: add garage single-node config for self-host stack | `Lef-F/mike` | 2026-05-04 |
| 7 | [`cd1678ae`](https://github.com/Lef-F/mike/commit/cd1678aedc36d5b168aed4f030c34505029bf0c4) | feat: add init-db script for applying mike schema | `Lef-F/mike` | 2026-05-04 |
| 8 | [`6e9c11f8`](https://github.com/Lef-F/mike/commit/6e9c11f81a30b85da3e80e8cc67d52f3d7f0354d) | feat: add init-garage script for bucket and key bootstrap | `Lef-F/mike` | 2026-05-04 |
| 9 | [`3a37c449`](https://github.com/Lef-F/mike/commit/3a37c4498f1f9f8ad4916a497e1cb72377893e94) | feat: add mike-backend Dockerfile with libreoffice | `Lef-F/mike` | 2026-05-04 |
| 10 | [`09f6be77`](https://github.com/Lef-F/mike/commit/09f6be77c84d0cb344edb4a0e22f49e5a74f32c3) | feat: add mike-frontend Dockerfile | `Lef-F/mike` | 2026-05-04 |
| 11 | [`2f46947f`](https://github.com/Lef-F/mike/commit/2f46947f2a707783d85db51cedfa7d6804160f58) | feat: add caddyfile ingress for self-host stack | `Lef-F/mike` | 2026-05-04 |
| 12 | [`ee25d150`](https://github.com/Lef-F/mike/commit/ee25d1507246d5ca9beabff9ed50306dfc873fd2) | feat: add docker-compose for self-host stack | `Lef-F/mike` | 2026-05-04 |
| 13 | [`9613b6bd`](https://github.com/Lef-F/mike/commit/9613b6bd20fcd73d5ae61234d491723cf64e67e9) | fix: resolve first-boot smoke test failures for Task 11 | `Lef-F/mike` | 2026-05-04 |
| 14 | [`8ff0dc8b`](https://github.com/Lef-F/mike/commit/8ff0dc8b72289e43e5ff937a569662548ece78cd) | docs: document docker-compose self-host workflow | `Lef-F/mike` | 2026-05-05 |
| 15 | [`9cc8453c`](https://github.com/Lef-F/mike/commit/9cc8453c851a4b432614cbb76d7c5baea1c3bc9f) | fix: route backend->gotrue through caddy with transparent host header | `Lef-F/mike` | 2026-05-05 |
| 16 | [`9f6dcfaf`](https://github.com/Lef-F/mike/commit/9f6dcfaf1d991c2916744a8f043ec79c2157b34f) | fix: align garage virtual-hosted-style routing for AWS S3 SDK | `Lef-F/mike` | 2026-05-05 |
| 17 | [`8d411844`](https://github.com/Lef-F/mike/commit/8d41184460c7c61ba13839acaa899b8e54c108a2) | perf: use Next.js standalone output for frontend image | `Lef-F/mike` | 2026-05-05 |
| 18 | [`0549bff6`](https://github.com/Lef-F/mike/commit/0549bff66c3369ae813102488ec84aa899909843) | chore: silence compose warning when only one LLM key is set | `Lef-F/mike` | 2026-05-05 |
| 19 | [`e59f59ea`](https://github.com/Lef-F/mike/commit/e59f59eaa97344418ec1366fc253bf01ded0c16a) | chore: drop unused MIKE_HOST from caddy + remove orphaned Dockerfile | `Lef-F/mike` | 2026-05-05 |
| 20 | [`9c7218a8`](https://github.com/Lef-F/mike/commit/9c7218a883439b2659d3d59e1b24c5df6a117841) | fix: add aud claim to minted JWTs in generate-secrets.sh | `Lef-F/mike` | 2026-05-05 |
| 21 | [`325510e6`](https://github.com/Lef-F/mike/commit/325510e6687d933b65accf31785832c52ffb649f) | Merge pull request #1 from Lef-F/lef/docker-compose | `Lef-F/mike` | 2026-05-05 |

### Commit URLs (for your tooling)

1. https://github.com/Lef-F/mike/commit/4038fe74d1b95ff509117cfe0ec17ab54b008aa2
2. https://github.com/Lef-F/mike/commit/2a9edadef963a43d971a48c784fd4eb820fc6178
3. https://github.com/Lef-F/mike/commit/6fe97e23266240e3b6c7022bdd8375a1bd96b7c6
4. https://github.com/Lef-F/mike/commit/c027e2e6ccd4e2aec8af63e35494f0b1858b20aa
5. https://github.com/Lef-F/mike/commit/9315240017701bacc924ac9489c1603d03cdca07
6. https://github.com/Lef-F/mike/commit/ff85a40894a4dd340afc3001360c1b554cfe441a
7. https://github.com/Lef-F/mike/commit/cd1678aedc36d5b168aed4f030c34505029bf0c4
8. https://github.com/Lef-F/mike/commit/6e9c11f81a30b85da3e80e8cc67d52f3d7f0354d
9. https://github.com/Lef-F/mike/commit/3a37c4498f1f9f8ad4916a497e1cb72377893e94
10. https://github.com/Lef-F/mike/commit/09f6be77c84d0cb344edb4a0e22f49e5a74f32c3
11. https://github.com/Lef-F/mike/commit/2f46947f2a707783d85db51cedfa7d6804160f58
12. https://github.com/Lef-F/mike/commit/ee25d1507246d5ca9beabff9ed50306dfc873fd2
13. https://github.com/Lef-F/mike/commit/9613b6bd20fcd73d5ae61234d491723cf64e67e9
14. https://github.com/Lef-F/mike/commit/8ff0dc8b72289e43e5ff937a569662548ece78cd
15. https://github.com/Lef-F/mike/commit/9cc8453c851a4b432614cbb76d7c5baea1c3bc9f
16. https://github.com/Lef-F/mike/commit/9f6dcfaf1d991c2916744a8f043ec79c2157b34f
17. https://github.com/Lef-F/mike/commit/8d41184460c7c61ba13839acaa899b8e54c108a2
18. https://github.com/Lef-F/mike/commit/0549bff66c3369ae813102488ec84aa899909843
19. https://github.com/Lef-F/mike/commit/e59f59eaa97344418ec1366fc253bf01ded0c16a
20. https://github.com/Lef-F/mike/commit/9c7218a883439b2659d3d59e1b24c5df6a117841
21. https://github.com/Lef-F/mike/commit/325510e6687d933b65accf31785832c52ffb649f

## What I want you to do

1.  **Sanity check first.**

    - Run `git status`. If the working tree is dirty (uncommitted
      changes you don't recognise, untracked stuff you don't expect),
      STOP and tell me — don't try to be helpful by stashing. I'll
      resolve it.
    - Run `git branch --show-current`. If the branch is `main` or
      `master`, confirm with me before proceeding.

2.  **For each commit URL above, in the order listed:**

    a.  Fetch the diff. Pick whichever works:
        - `gh api repos/<owner>/<repo>/commits/<sha>` returns the full
          patch in JSON.
        - WebFetch the URL with `.patch` appended, e.g.
          `https://github.com/<owner>/<repo>/commit/<sha>.patch`.

    b.  Read the original commit message. That's the AUTHOR's intent —
        respect it.

    c.  Read the diff and understand the change. **Don't blindly
        cherry-pick.** This is a sibling fork — paths, naming, and
        structure can differ. You're porting, not pasting.

    d.  Compare against THIS repo's layout:
        - File at the same path → apply the change.
        - File exists under a different name (renamed / restructured) →
          apply the equivalent change at the right location.
        - File doesn't exist here at all → decide: new file we want, or
          is the source adding something this repo already has by
          another name? Use judgement. Lean towards creating the file
          when in doubt — easier for me to delete than to recreate.

    e.  Apply the change. Run `git diff` after, eyeball it, fix
        obvious issues (lint errors, broken imports, typos in the diff
        itself).

    f.  Commit with a message that:
        - Preserves the source commit's subject line.
        - Adds a short body explaining what you adapted, if anything.
        - Includes trailers:

              Source: <commit-url>
              Source-author: <original author name>

        so the attribution stays clear.

3.  **After all commits are applied:**

    - Run `git log --oneline -<count>` showing what you produced.
    - Show `git status` final state.
    - List any files you skipped, conflicts you resolved, and any
      assumptions you made.

## Rules

- **Do not push.** Local commits only. I'll review and push.
- **Do not rebase or force.** Only fresh commits. If you'd otherwise
  need a force push, stop and explain why.
- **Don't touch `.git/config` or run `git remote add`.** Leave my
  repo's remote setup alone.
- **No package installs, build steps, or migrations** unless the
  change manifestly requires it AND you explicitly tell me what
  you're about to run first.
- **One commit per source commit.** Don't squash. Don't split. If
  porting genuinely requires either, explain.
- **Read existing code before changing it.** This isn't the source
  fork. Match the local style.

## If you get stuck

Stop and tell me. Show what you've already done (commits made, files
changed), what blocked you (conflict, missing file, ambiguous intent),
and your recommended next move. I'd rather ship 3 of 5 commits cleanly
than have you guess on the 4th and break things.