Rename tline to porthole
This commit is contained in:
28
README.md
28
README.md
@@ -10,13 +10,13 @@ Porthole: timeline media library (Next.js web + worker), backed by Postgres/Redi
|
||||
- set `images.web.repository/tag` and `images.worker.repository/tag`
|
||||
- set `global.tailscale.tailnetFQDN` (recommended), or set `app.minio.publicEndpointTs` (must be `https://minio.<tailnet-fqdn>`)
|
||||
|
||||
- Render locally: `helm template porthole helm/tline -f your-values.yaml --namespace porthole`
|
||||
- Render locally: `helm template porthole helm/porthole -f your-values.yaml --namespace porthole`
|
||||
|
||||
- Install (to `porthole` namespace): `helm upgrade --install porthole helm/tline -f your-values.yaml --namespace porthole`
|
||||
- Install (to `porthole` namespace): `helm upgrade --install porthole helm/porthole -f your-values.yaml --namespace porthole`
|
||||
|
||||
## ArgoCD
|
||||
|
||||
A ready-to-apply ArgoCD `Application` manifest is included at `argocd/tline-application.yaml` (it deploys the Helm release name `porthole`).
|
||||
A ready-to-apply ArgoCD `Application` manifest is included at `argocd/porthole-application.yaml` (it deploys the Helm release name `porthole`).
|
||||
|
||||
Reference example (deploys into the `porthole` namespace; the Helm chart itself does not hardcode a namespace):
|
||||
|
||||
@@ -31,7 +31,7 @@ spec:
|
||||
source:
|
||||
repoURL: git@gitea-gitea-ssh.taildb3494.ts.net:will/porthole.git
|
||||
targetRevision: main
|
||||
path: helm/tline
|
||||
path: helm/porthole
|
||||
helm:
|
||||
releaseName: porthole
|
||||
valueFiles:
|
||||
@@ -41,8 +41,8 @@ spec:
|
||||
# parameters:
|
||||
# - name: global.tailscale.tailnetFQDN
|
||||
# value: tailxyz.ts.net
|
||||
# - name: images.web.repository
|
||||
# value: registry.lan:5000/tline-web
|
||||
# - name: images.web.repository
|
||||
# value: registry.lan:5000/porthole-web
|
||||
# - name: images.web.tag
|
||||
# value: dev
|
||||
destination:
|
||||
@@ -89,25 +89,25 @@ This repo is a Bun monorepo, but container builds use Docker Buildx.
|
||||
- Your Docker daemon is configured to allow that registry as an insecure registry.
|
||||
|
||||
- Create/use a buildx builder (one-time):
|
||||
- `docker buildx create --name tline --use`
|
||||
- `docker buildx create --name porthole --use`
|
||||
|
||||
- Build + push **web** (Next standalone):
|
||||
- `REGISTRY=registry.lan:5000 TAG=dev`
|
||||
- `docker buildx build --platform linux/amd64,linux/arm64 -f apps/web/Dockerfile -t "$REGISTRY/tline-web:$TAG" --push .`
|
||||
- `docker buildx build --platform linux/amd64,linux/arm64 -f apps/web/Dockerfile -t "$REGISTRY/porthole-web:$TAG" --push .`
|
||||
- Notes:
|
||||
- The Dockerfile uses `bun install --frozen-lockfile` and copies all workspace `package.json` files first to keep Bun from mutating `bun.lock`.
|
||||
- Runtime entrypoint comes from Next standalone output (the image runs `node app/apps/web/server.js`).
|
||||
|
||||
- Build + push **worker** (includes `ffmpeg` + `exiftool`):
|
||||
- `REGISTRY=registry.lan:5000 TAG=dev`
|
||||
- `docker buildx build --platform linux/amd64,linux/arm64 -f apps/worker/Dockerfile -t "$REGISTRY/tline-worker:$TAG" --push .`
|
||||
- `docker buildx build --platform linux/amd64,linux/arm64 -f apps/worker/Dockerfile -t "$REGISTRY/porthole-worker:$TAG" --push .`
|
||||
- Notes:
|
||||
- The Dockerfile uses `bun install --frozen-lockfile --production` and also copies all workspace `package.json` files first for stable `workspace:*` resolution.
|
||||
|
||||
- Then set Helm values:
|
||||
- `images.web.repository: registry.lan:5000/tline-web`
|
||||
- `images.web.repository: registry.lan:5000/porthole-web`
|
||||
- `images.web.tag: dev`
|
||||
- `images.worker.repository: registry.lan:5000/tline-worker`
|
||||
- `images.worker.repository: registry.lan:5000/porthole-worker`
|
||||
- `images.worker.tag: dev`
|
||||
|
||||
### Private registry auth (optional)
|
||||
@@ -167,7 +167,7 @@ This chart assumes you label nodes like:
|
||||
- Pi 5 nodes: `node-class=compute`
|
||||
- Pi 3 node: `node-class=tiny`
|
||||
|
||||
The default scheduling in `helm/tline/values.yaml` pins heavy pods to `node-class=compute`.
|
||||
The default scheduling in `helm/porthole/values.yaml` pins heavy pods to `node-class=compute`.
|
||||
|
||||
Example `values.yaml` you can start from:
|
||||
|
||||
@@ -181,10 +181,10 @@ secrets:
|
||||
|
||||
images:
|
||||
web:
|
||||
repository: registry.lan:5000/tline-web
|
||||
repository: registry.lan:5000/porthole-web
|
||||
tag: dev
|
||||
worker:
|
||||
repository: registry.lan:5000/tline-worker
|
||||
repository: registry.lan:5000/porthole-worker
|
||||
tag: dev
|
||||
|
||||
global:
|
||||
|
||||
Reference in New Issue
Block a user