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>
15 lines
451 B
YAML
15 lines
451 B
YAML
# Copy to secret.yaml (gitignored), set real values, apply once per cluster.
|
|
# Carried over from the CasaOS deployment -- NEXTAUTH_SECRET signs existing
|
|
# sessions and MEILI_MASTER_KEY unlocks the existing index, so these must be
|
|
# the SAME values, not fresh ones.
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: karakeep
|
|
namespace: karakeep
|
|
type: Opaque
|
|
stringData:
|
|
meili-master-key: CHANGEME
|
|
nextauth-secret: CHANGEME
|
|
openai-api-key: CHANGEME
|