Initial setup: OpenResto deployment for Lunkaberg breakfast booking
Adapts upstream's release docker-compose.yml to run behind this server's Nginx Proxy Manager on the shared my-main-net network instead of publishing host ports. Includes docs/ for session continuity. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014vNjtg18oTQcv8dtjwnT69
This commit is contained in:
@@ -0,0 +1,28 @@
|
||||
# Decisions — Lunkaberg Frukost (OpenResto)
|
||||
|
||||
## 2026-09-21 — Use OpenResto rather than build custom
|
||||
Per wanted to evaluate get.openres.to for a client breakfast-booking site.
|
||||
It's MIT-licensed, self-hosted, ASP.NET Core + React + SQLite, ships
|
||||
pre-built multi-arch Docker images and is explicitly designed to sit behind
|
||||
a reverse proxy like NPM. Decided to deploy it as-is rather than build a
|
||||
custom PHP tool, since it already covers table holds, multi-location,
|
||||
service periods, and an admin dashboard out of the box.
|
||||
|
||||
## 2026-09-21 — Git via self-hosted Gitea, not the usual live-edit workflow
|
||||
Per's standing default for hobby projects is no git / live-editing on the
|
||||
server. This is client work, so he's using his Gitea instance
|
||||
(gitea.axbom.com) instead — repo `root/LunkabergB`. `.env` (secrets) is
|
||||
gitignored; `.env.example` documents the required variables.
|
||||
|
||||
## 2026-09-21 — No host ports published for the OpenResto containers
|
||||
Upstream's docker-compose.yml publishes the bundled nginx reverse-proxy
|
||||
container on host port 80 by default, which would collide with this
|
||||
server's Nginx Proxy Manager (already bound to 80/443). Adapted the compose
|
||||
file to join the existing `my-main-net` Docker network instead (same
|
||||
pattern as vox, remark42, etc.) — NPM proxies straight to
|
||||
`lunkaberg-reverse-proxy:80` over the Docker network, no host port needed.
|
||||
|
||||
## 2026-09-21 — Admin email defaulted to per@axbom.se
|
||||
Used as a placeholder so there's a working login immediately; this should
|
||||
be revisited once it's clear who administers bookings day-to-day for the
|
||||
client (Per vs. someone at Lunkaberg).
|
||||
Reference in New Issue
Block a user