jasonwittyandClaude Opus 5
00a1742b85
Three containers move across as three deployments: the app, meilisearch, and
the headless-chrome renderer. Data (4.2M of SQLite + assets, 3.3M meilisearch
index) copied from /DATA/AppData/karakeep on the Orange Pi to gvolume0 at
/mnt/gvolume0/karakeep/{data,meilisearch}.
MEILI_MASTER_KEY and NEXTAUTH_SECRET are carried over unchanged, not
regenerated -- the first unlocks the existing index and the second signs
existing sessions. OPENAI_API_KEY was already empty on CasaOS, so AI tagging
was unused; the key is kept but blank.
NEXTAUTH_URL changes from http://localhost:14592 to https://keep.wittyoneoff.com
so NextAuth builds correct callback URLs behind the proxy.
chrome.yaml passes EXACTLY the args the CasaOS container used. Adding
--remote-debugging-address/--remote-debugging-port breaks it: the image's
entrypoint runs Chrome on 127.0.0.1:9223 and socat-proxies 9222 -> 9223, so
overriding those flags leaves socat retrying a dead port forever. Learned the
hard way.
App and meilisearch use strategy: Recreate -- single-writer SQLite on a
ReadWriteOnce volume, same rule as apps/tududi.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 lines
342 B
YAML
13 lines
342 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
# secret.example.yaml is intentionally NOT listed -- copy it to secret.yaml
|
|
# (gitignored), set real values, and apply it once per cluster.
|
|
resources:
|
|
- namespace.yaml
|
|
- storage.yaml
|
|
- deployment.yaml
|
|
- meilisearch.yaml
|
|
- chrome.yaml
|
|
- service.yaml
|
|
- ingress.yaml
|