Skip to content

🍴 Kouizine

kouizine_banner

Rust — axum + tokio React — TypeScript + Vite PostgreSQL PWA — offline-first Version 1.0.0

Kouizine is a self-hosted recipe website with a shopping-list twist: browse the recipes, put some in the panier with the number of parts you want to cook, and get an aggregated, checkable liste de courses — with a sankey diagram and a PDF export.

Introduction

The public site shows the recipes of selected users (home grid, one public page per user, one page per recipe); accounts are invite-only and each user edits their own recipes. The panier works signed-out, stored in the browser (signed in, it follows the account across its devices), and scales the aggregated shopping list by the parts chosen per recipe.

This page covers installing and running the application as a self-contained web service.

Info

Kouizine is open-source and lives in this repository under src/ (Rust backend + React/TypeScript frontend), with the Podman packaging in build/, quadlet/ and nginx/, and the one-time recipe import in seed/.

Features

  • 🍽️ Public home grid of selected users' recipes, /username pages, recipe pages with cover, prep table, ingredients, steps and optional video
  • 📝 Structured ingredients (quantité / unité française / nom) + markdown intro and steps, edited with a live preview
  • 🖼️ Per-recipe thumbnail and movie uploads (UUID-named files under the data directory); a photo added or removed offline applies at once and syncs in the background
  • 🧺 Panier: select recipes, set parts, generate the scaled shopping list, tick items off at the store; signed in, the basket and the ticks follow the account across its devices
  • 📄 PDF export with clickable checkboxes and the ingredients→recipes sankey diagram
  • 🔐 Invite-only accounts with emailed activation links and optional TOTP 2FA — one admin invites the others; the owner's email change from the profile is confirmed through a link mailed to the new address (French /confirm-email page), and the account keeps its current address until then; an admin's change is written at once: an active account's old and new addresses each get a French notice, a pending account's corrected address a new invitation; an admin changes their own address from the profile only
  • 👤 Profile picture on Réglages, the platform's: add, change or remove it; a JPEG XL is decoded in the browser, the crop saved as a 512 px JPEG, shown on the menubar's avatar and in the user menu and kept on the device for an offline start
  • 📴 Local-first PWA: installable, and signed in the recipes, the ingredient registry and the account's basket and ticks live on the device — every page opens instantly with no network, edits, basket changes and recipe photos made offline sync in the background, other devices' changes arrive without a reload; a dot on the menubar's avatar says whether the server answers, another in the user menu says offline / pending / synced; movie uploads, movie playback, movie removal and changing the profile picture need a connection (offline & sync)

How it works

Web UI cooks: local-first visitors: REST axum API serves the SPA imports seed/ once PostgreSQL recipes · basket ingredients · ticks users · sessions REST · sync SSE data/recipes thumbnails · movies UUID names seed/ 39 legacy recipes shipped in the image
Recipes sync for signed-in cooks; visitors read the public routes.

The backend binary serves both the API and the built React SPA. Recipes, users and sessions live in PostgreSQL; the uploaded media (thumbnails, movies, profile pictures) are stored as files under the data directory, so the database stays small. On the first successful boot the 39 legacy markdown recipes shipped in seed/ are imported once. Signed in, the installed PWA keeps the recipes and the ingredient registry on the device (IndexedDB, the thumbnails in the platform service worker's cache) and syncs them through /api/sync, the server announcing changes over SSE; a new photo waits on the device until it uploads. Signed-out visitors read the public REST routes.

📥 Installation

This section describes how to install and run Podman services using systemd Quadlet, enabling containers to restart automatically. It allows the service to run in its own isolated rootless environment with a dedicated Linux user.

📋 Requirements

Info

Kouizine requires the installation of

⚙️ Configuration

📋 Service Setup

Info

Please follow the following installation steps:

Define Service Variables

# define the service name
SERVICE_NAME=kouizine
Initialize Service Environment 
# built-in bash safety and SERVICE_NAME validation
set -euo pipefail; [ -n "${SERVICE_NAME:-}" ] || { echo "SERVICE_NAME is empty"; exit 1; }

# automatically generate variables
SERVICE_HOME="/media/ssd/podman-users/${SERVICE_NAME}"
SERVICE_DIR="/media/ssd/podman/${SERVICE_NAME}"
SERVICE_USER="${SERVICE_NAME}_svc"
SERVICE_ADMIN="${SERVICE_NAME}_admins"

🔐 Service Isolation

Configure Rootless Podman UID/GID Namespace Mappings 
# allocate rootless Podman UID/GID mappings if missing
SUBID_SIZE=65536
allocate_subids_if_missing() {
  local user="$1"
  local start
  if ! grep -q "^${user}:" /etc/subuid; then
    start="$(awk -F: 'BEGIN { max = 100000 } { end = $2 + $3; if (end > max) max = end } END { print max }' /etc/subuid)"
    sudo usermod --add-subuids "${start}-$((start + SUBID_SIZE - 1))" "$user"
  fi
  if ! grep -q "^${user}:" /etc/subgid; then
    start="$(awk -F: 'BEGIN { max = 100000 } { end = $2 + $3; if (end > max) max = end } END { print max }' /etc/subgid)"
    sudo usermod --add-subgids "${start}-$((start + SUBID_SIZE - 1))" "$user"
  fi
}
allocate_subids_if_missing "${SERVICE_USER}"

# verify rootless Podman UID/GID namespace mappings exist
grep -q "^${SERVICE_USER}:" /etc/subuid || { echo "ERROR: missing subuid mappings for ${SERVICE_USER}"; exit 1; }
grep -q "^${SERVICE_USER}:" /etc/subgid || { echo "ERROR: missing subgid mappings for ${SERVICE_USER}"; exit 1; }

# validate that all subordinate ID ranges in a file are non-overlapping
validate_subid_ranges() {
  local file="$1"
  awk -F: '
    {
      start = $2
      end   = $2 + $3 - 1
      for (i = 1; i <= count; i++) {
        if (start <= ends[i] && end >= starts[i]) {
          printf "ERROR: overlapping ranges in %s\n", FILENAME
          printf "  %s:%s:%s overlaps %s:%s:%s\n",
            $1, $2, $3,
            names[i], starts[i], sizes[i]
          exit 1
        }
      }
      count++
      names[count]  = $1
      starts[count] = start
      ends[count]   = end
      sizes[count]  = $3
    }
  ' "$file"
}
validate_subid_ranges /etc/subuid
validate_subid_ranges /etc/subgid

# configure the rootless storage driver BEFORE Podman first initializes its storage.
# fuse-overlayfs is a reliable rootless overlay backend and avoids kernel-version
# quirks of native rootless overlay on ARM/Armbian. It is optional with the default
# userns used here, but recommended; set it before the first storage init so no
# 'podman system reset' is needed later.
sudo -u "${SERVICE_USER}" mkdir -p "${SERVICE_HOME}/.config/containers"
sudo -u "${SERVICE_USER}" tee "${SERVICE_HOME}/.config/containers/storage.conf" >/dev/null <<'EOF'
[storage]
driver = "overlay"

[storage.options.overlay]
mount_program = "/usr/bin/fuse-overlayfs"
EOF

# rebuild rootless Podman state to ensure existing containers/storage use current namespace mappings
# use a login shell (-i) so HOME points at the service user's home
# (storage now initializes with fuse-overlayfs; no 'podman system reset' needed)
sudo -iu "${SERVICE_USER}" podman system migrate
Configure Secure Service Directory Permissions 
# Apply the admin/service ACL policy to one directory tree, deterministically.
#   $1 = tree to treat
#   $2 = (optional) a sub-path to skip entirely (e.g. a container data subtree)
#
# Why setfacl, not chmod: on an ACL'd tree, chmod edits only the mask, never group::,
# so stale execute bits survive. setfacl sets every entry explicitly (mask included),
# lowercase — the result is reproducible and no execute bit can resurface.
apply_acl_tree() {
    local tree="$1"
    local skip="${2:-}"
    local prune=()
    [ -n "$skip" ] && prune=( -path "$skip" -prune -o )                                         # skip this subtree if a 2nd arg is given

    sudo find "$tree" "${prune[@]}" -exec chown "${SERVICE_USER}:${SERVICE_ADMIN}" {} +         # service user owns; admin group is the owning group

    # directories — access ACL (perms on the existing dirs)
    sudo find "$tree" "${prune[@]}" -type d -exec setfacl    -m g:${SERVICE_ADMIN}:rwx {} +     # admin group: access existing dirs
    sudo find "$tree" "${prune[@]}" -type d -exec setfacl    -m u:${SERVICE_USER}:rwx {} +      # service user: access existing dirs
    sudo find "$tree" "${prune[@]}" -type d -exec setfacl    -m u::rwx,g::rwx,o::-,m::rwx {} +  # owner/group rwx, deny others, pin mask rwx

    # directories — default ACL (inherited by NEW files/dirs created later)
    sudo find "$tree" "${prune[@]}" -type d -exec setfacl -d -m g:${SERVICE_ADMIN}:rwx {} +     # admin group: inherit access on new items
    sudo find "$tree" "${prune[@]}" -type d -exec setfacl -d -m u:${SERVICE_USER}:rwx {} +      # service user: inherit access on new items
    sudo find "$tree" "${prune[@]}" -type d -exec setfacl -d -m u::rwx,g::rwx,o::- {} +         # default owner/group/other for new items

    # files — access ACL (rw only, never executable)
    sudo find "$tree" "${prune[@]}" -type f -exec setfacl    -m g:${SERVICE_ADMIN}:rw {} +      # admin group: access existing files
    sudo find "$tree" "${prune[@]}" -type f -exec setfacl    -m u:${SERVICE_USER}:rw {} +       # service user: access existing files
    sudo find "$tree" "${prune[@]}" -type f -exec setfacl    -m u::rw,g::rw,o::-,m::rw {} +     # owner/group rw, deny others, pin mask rw

    sudo find "$tree" "${prune[@]}" -type d -exec chmod g+s {} +                                # setgid: new items inherit the group (a MODE bit; ACLs can't set it)
}

# --- SERVICE_HOME: Podman's private runtime home ------------------------------
# Own the home + set setgid, then ACL ONLY the .config subtree (containers.conf,
# storage.conf, and the *.network / *.container quadlets you hand-edit) so admins
# can edit them sudo-less.
#
# Leave ~/.local (storage) and ~/.cache to Podman: ACLs on the overlay store break
# the runtime ("OCI permission denied" on the `merged` mount). Admin reaches them via sudo.
sudo chown "${SERVICE_USER}:${SERVICE_ADMIN}" "${SERVICE_HOME}"                       # service user owns; admin group is the owning group
sudo chmod u=rwx,g=rwx,o=,g+s "${SERVICE_HOME}"                                       # owner/admin access; deny others; inherit group on new items
apply_acl_tree "${SERVICE_HOME}/.config"                                              # .config subtree: full sudo-less admin ACL treatment

# --- bind-mount data dirs: created + owned BEFORE the SERVICE_DIR ACL pass ---------
# Each container writes as a mapped subuid, so its data dir must be owned by that subuid
# (chown as root; only root crosses the id range). We create + own them FIRST so they
# neither inherit SERVICE_DIR's default ACL (inheritance happens at creation) nor get
# walked by apply_acl_tree (which prunes data/).
#
# No ACLs here: Postgres refuses a group-accessible PGDATA. Admin reaches them via sudo;
# back Postgres up with pg_dumpall, not a raw file copy.
SUBUID_BASE="$(awk -F: -v u="${SERVICE_USER}" '$1==u {print $2}' /etc/subuid)"
SUBGID_BASE="$(awk -F: -v u="${SERVICE_USER}" '$1==u {print $2}' /etc/subgid)"

# data subdir : in-container uid/gid it must be owned by
data_dirs=(
    "postgres-db:70"          # /var/lib/postgresql — postgres user (pinned User=70:70)
    "recipes:1000"            # /data/recipes       — recipe media and profile picture uploads (image USER 1000)
)

mkdir -p "${SERVICE_DIR}/data"                                                        # the data/ parent: plain, no ACL
sudo chown "${SERVICE_USER}:${SERVICE_ADMIN}" "${SERVICE_DIR}/data"                   # owner/admin
sudo chmod 0750 "${SERVICE_DIR}/data"                                                 # children are set individually below
for entry in "${data_dirs[@]}"; do
    sub="${entry%%:*}"                                  # subdir name
    ids="${entry#*:}"                                   # "uid" or "uid:gid"
    uid="${ids%%:*}"                                    # uid
    gid="${ids#*:}"; [ "$gid" = "$ids" ] && gid="$uid"  # gid (defaults to uid)
    dir="${SERVICE_DIR}/data/${sub}"
    sudo mkdir -p "$dir"
    sudo chown -R "$((SUBUID_BASE + uid - 1)):$((SUBGID_BASE + gid - 1))" "$dir"   # map both to host subids
    sudo chmod 0700 "$dir"
done

# --- SERVICE_DIR: application data, env files, configuration -------------------
# Full treatment so the admin group gets sudo-less access AND the service user keeps
# access even on admin-created files. data/ is EXCLUDED: those dirs are owned by the
# containers' subuids and need engine-specific modes (Postgres rejects a group/other-
# accessible PGDATA), so they are handled separately just below.
apply_acl_tree "${SERVICE_DIR}" "${SERVICE_DIR}/data"                                 # treat everything EXCEPT data/
Configure Secure NGINX Static Assets Permissions 
# Grant the NGINX worker user (www-data) read-only access to assets subtrees.
#   $1     = service directory → traverse-only (x)
#   $2..$n = assets subtrees served directly by NGINX (configs, icons, favicon, manifest, ...)
apply_acl_nginx() {
    local tree="$1"; shift
    local assets

    sudo setfacl -m u:www-data:x "$tree"                                        # traverse only: pass through, no listing, no reading

    for assets in "$@"; do
        # assets directories — enter + list, existing and future
        sudo find "$assets" -type d -exec setfacl    -m u:www-data:rx {} +      # www-data: read existing dirs
        sudo find "$assets" -type d -exec setfacl -d -m u:www-data:rx {} +      # www-data: inherit read on new items

        # assets files — www-data read-only, owner/admin rw, never executable.
        # Entries AND mask are pinned explicitly: a bare `setfacl -m u:www-data:r`
        # would recalculate the mask to the union of all entries, resurfacing the
        # latent rwx inherited from the default ACL (files would show group rwx).
        sudo find "$assets" -type f -exec setfacl \
          -m u:www-data:r,u:${SERVICE_USER}:rw,g:${SERVICE_ADMIN}:rw,u::rw,g::rw,o::-,m::rw {} +
    done
}

# --- SERVICE_DIR/nginx: served directly by NGINX -----------
# Created AFTER the apply_acl_tree pass so they inherit the default ACL + setgid
# group (service user/admin keep full access); www-data is then layered on top
# as a read-only named entry.
sudo mkdir -p "${SERVICE_DIR}/nginx"
sudo chown "${SERVICE_USER}:${SERVICE_ADMIN}" "${SERVICE_DIR}/nginx"
apply_acl_nginx "${SERVICE_DIR}" "${SERVICE_DIR}/nginx"

🛡️ Rootless Podman Defaults

Configure rootless Podman per-user configuration directory 
# configure rootless Podman defaults for this service user
# - store per-user Podman configuration under ~/.config/containers
sudo -u "${SERVICE_USER}" mkdir -p "${SERVICE_HOME}/.config/containers/systemd"
Configure rootless Podman defaults 
# configure rootless Podman defaults for this service user
# - use k8s-file logging for easier log rotation and inspection
sudo -u "${SERVICE_USER}" tee "${SERVICE_HOME}/.config/containers/containers.conf" >/dev/null <<EOF
[containers]
log_driver = "k8s-file"

[engine]
healthcheck_events=false
EOF

🔧 Service Configuration

Setup Kouizine Parameters

Before deploying, you need to define a few environment variables that will be used throughout the setup process.

  • BASE_URL: public URL where the web service is accessible
  • HOST_PORT: external port used by NGINX to route traffic to the service
  • ADMIN_EMAIL: the default admin account (email only — there is no admin password in the env)
  • SMTP settings: required so the admin and invited users receive their activation links (startup aborts if the relay is unreachable)
###################################################################################
# NGINX Proxy Configuration
###################################################################################
HOST_PORT=10050

###################################################################################
# Postgres Configuration
###################################################################################
PG_VERSION=18-alpine
PG_DB=kouizine
PG_USER=kouizine
PG_PASSWORD="$(openssl rand -hex 32)"

###################################################################################
# Kouizine Configuration
###################################################################################
BASE_URL=https://kouizine.domain.fr
ADMIN_EMAIL=admin@domain.fr

###################################################################################
# SMTP Configuration
###################################################################################
SMTP_HOST=smtp.gmail.com
SMTP_PORT=587
SMTP_SECURITY=starttls
SMTP_USER=kouizine@domain.fr
SMTP_PASSWORD=your-smtp-password
SMTP_FROM=kouizine@domain.fr

Getting Your Gmail SMTP Password

To send emails via Gmail SMTP, you'll need to generate an App Password.
A special password used for third-party applications.
Visit myaccount.google.com/apppasswords to create one.

Use the generated password in the SMTP_PASSWORD field of your configuration.

Create the Environment file 
sudo -u "${SERVICE_USER}" tee "${SERVICE_DIR}/postgres.env" >/dev/null <<EOF
###################################################################################
# Postgres Database Configuration
###################################################################################
POSTGRES_VERSION=${PG_VERSION}
POSTGRES_DB=${PG_DB}
POSTGRES_USER=${PG_USER}
POSTGRES_PASSWORD=${PG_PASSWORD}
EOF

sudo -u "${SERVICE_USER}" tee "${SERVICE_DIR}/kouizine.env" >/dev/null <<EOF
###################################################################################
# NGINX Proxy Configuration
###################################################################################
HOST_PORT=${HOST_PORT}

###################################################################################
# Base image versions (build)
###################################################################################
RUST_VERSION=1.98.0
NODE_VERSION=24
DEBIAN_TAG=trixie-slim

###################################################################################
# Kouizine Configuration
###################################################################################
KOUIZINE_BASE_URL=${BASE_URL}
KOUIZINE_COOKIE_SECURE=true

###################################################################################
# Default admin (seeded 'pending' on first start)
###################################################################################
KOUIZINE_ADMIN_EMAIL=${ADMIN_EMAIL}

###################################################################################
# SMTP (required for new-user validation emails)
###################################################################################
SMTP_HOST=${SMTP_HOST}
SMTP_PORT=${SMTP_PORT}
SMTP_SECURITY=${SMTP_SECURITY}
SMTP_USER=${SMTP_USER}
SMTP_PASSWORD=${SMTP_PASSWORD}
SMTP_FROM=${SMTP_FROM}
EOF

Keep the .env files

All the secret informations will be stored in the .env files.

Optional tunables (defaults shown in kouizine.prod.env.example): KOUIZINE_SESSION_TTL_HOURS=720, KOUIZINE_ACTIVATION_TTL_HOURS=72, KOUIZINE_MAX_IMAGE_MB=10, KOUIZINE_MAX_MOVIE_MB=200.

🧩 Quadlet Service

Install the Quadlet units 
# the units live in the repository under quadlet/ — every .build unit already
# carries the platform build context:
#   PodmanArgs=--build-context platform=/media/ssd/podman/platform
# link them into the service user's systemd directory (the generator and
# podmanctl read them there). Re-runnable: every existing link into quadlet/
# is dropped first — stale or dangling ones included — then the current set
# is linked, replacing a plain file of the same name if one is left over.
# find runs from / : GNU find returns to its starting directory when done, and a
# directory the service user cannot enter (the admin's home, mode 700) fails it — AFTER
# the delete, so a `set -e` shell would stop before relinking
(cd / && sudo -u "${SERVICE_USER}" find "${SERVICE_HOME}/.config/containers/systemd" -maxdepth 1 -type l -lname "${SERVICE_DIR}/quadlet/*" -delete)
sudo -u "${SERVICE_USER}" ln -sf "${SERVICE_DIR}"/quadlet/* "${SERVICE_HOME}/.config/containers/systemd/"

Symlinks, so a pull that edits a unit is live at the next systemctl --user daemon-reload (podmanctl --update reloads after its pull). A pull that adds, renames or removes a unit needs the two lines again, then the reload — quadlet changes are rare and deliberate.

Enable and Start Quadlet Services 
# open an interactive shell as the service user
sudo -iu "${SERVICE_USER}"

# reload systemd user units
systemctl --user daemon-reload

# build the kouizine image (first install; podmanctl --update rebuilds afterwards)
systemctl --user start kouizine-build.service

# start Podman Quadlet services
systemctl --user start kouizine-server.service

# verify service status
systemctl --user status kouizine-server.service

To follow the service logs in real time, run sudo journalctl _UID=$(id -u ${SERVICE_USER}) -f from the Debian account.

🚀 Deploy Kouizine

Install NGINX

NGINX needs to be installed, follow the NGINX section.

Configure NGINX

NGINX needs to be configured using a file in /etc/nginx/sites-enabled directory.
This configuration file specify the documentation path:

# Per-client rate-limit bucket for the auth endpoints (login is Argon2-costly;
# activate consumes single-use tokens). Must live in http{} context, so it sits
# outside the server{} block.
# $limit_key is the shared key from nginx.conf: the address for IPv4, the /64 prefix
# for IPv6 — keying on a full IPv6 address would let one subscriber prefix mint 2^64
# empty buckets and bypass the limit entirely.
limit_req_zone $limit_key zone=kouizine_auth:10m rate=10r/m;

# Per-client bucket for the liveness probe. Its own zone, NOT a share of the
# auth one: while offline the app probes /api/health every 15 s per tab, and at
# the auth zone's 10r/m that traffic ate the bucket a login needs — a household
# with a few tabs open could 429 its own sign-in. Generous on purpose (the app
# probes only while it believes it is offline); the point is a ceiling, not a brake.
limit_req_zone $limit_key zone=kouizine_health:10m rate=60r/m;

# Per-client connection buckets for the two SSE streams — long-lived by design
# (one per open tab), so they are capped per source IP rather than rate-limited.
# The app caps the total itself; these only stop one client from holding every
# worker connection.
limit_conn_zone $limit_key zone=kouizine_events:10m;
limit_conn_zone $limit_key zone=kouizine_sync_events:10m;

# Media uploads (contracts/files.md): writes (PUT, DELETE) are rate-limited per
# source IP so a client cannot churn the app's staging area; GETs pass freely —
# a device fills its cache with every recipe thumbnail at once. limit_req skips
# an empty key.
map $request_method $kouizine_upload_key {
  default $limit_key;
  GET     "";
  HEAD    "";
}
limit_req_zone $kouizine_upload_key zone=kouizine_uploads:10m rate=120r/m;

# The app container, published on the loopback by its Quadlet unit. It sits
# behind an upstream block for one reason: `keepalive`. Without it nginx opens —
# and immediately closes — a brand-new TCP connection for EVERY proxied request,
# and on this host each of those crosses rootless Podman's userspace port
# forwarder. The home grid is one thumbnail per recipe on top of the SPA
# assets, so a single page load paid a handshake per card through that
# forwarder and the thumbnails trickled in.
# `proxy_http_version 1.1` (already set in every location) and
# `proxy_set_header Connection ""` are what let a connection go back into this
# pool instead of being torn down.
upstream kouizine_app {
  server 127.0.0.1:10050;
  keepalive 32;
  keepalive_requests 1000;
  keepalive_timeout 60s;
}

server {
  server_name kouizine.domain.fr;

  # Security headers; `always` also covers the NGINX-served error pages. No
  # Content-Security-Policy here: the app serves its own on every response
  # (src/backend/src/web.rs) with the allowances its features need (data:/blob:
  # images, blob: media).
  # Browsers enforce EVERY CSP header they receive, so a second, stricter
  # proxy policy would silently break those features — keep the app's CSP the
  # single source of truth.
  add_header Strict-Transport-Security "max-age=63072000; includeSubDomains" always;
  add_header X-Content-Type-Options "nosniff" always;
  add_header X-Frame-Options "DENY" always;
  add_header Referrer-Policy "strict-origin-when-cross-origin" always;

  # The app sends these four itself (platform-http's security headers, HSTS
  # once its cookies are Secure): hidden here, so each reaches the browser once,
  # with the values above. A browser keeps only the FIRST HSTS header it gets,
  # and the app's (one year) came first.
  proxy_hide_header Strict-Transport-Security;
  proxy_hide_header X-Content-Type-Options;
  proxy_hide_header X-Frame-Options;
  proxy_hide_header Referrer-Policy;

  # setup 404 error_page
  error_page 404 /404.html;
  include snippets/error-404.conf;

  # show maintenance page when backend is down
  error_page 502 503 504 /maintenance.html;
  include snippets/error-maintenance.conf;

  # The backend answers unknown /api/* paths with a JSON 404 and every other path
  # with the SPA (200), so the only 404 that ever reaches us from upstream is an
  # API error. proxy_intercept_errors is on globally, which would swap that JSON
  # body for the HTML page and leave the UI parsing markup as JSON. NGINX's own
  # errors are unaffected — an unreachable container still gets the maintenance
  # page, because NGINX generates that 502 itself rather than proxying it.
  proxy_intercept_errors off;

  # Default ceiling for the whole vhost. Everything except the recipe media and
  # the sync batch posts small JSON, so 1 MB is generous — and it matters that
  # this is the default: nginx buffers a request body to disk BEFORE opening the
  # upstream connection, so a server-wide 210m would let an unauthenticated
  # client spool 210 MB to client_body_temp against any path (`/`, `/api/auth/me`,
  # `/favicon.ico`) and fill the proxy host's disk long before the app returns
  # 401. The media routes and /api/sync raise it for themselves below.
  client_max_body_size 1m;

  # Every unauthenticated auth endpoint, rate-limited before hitting the app
  # (contracts/auth.md): a public route the platform router gains is added here —
  # confirm-email shares the engine's per-IP lockout with activate, this is the
  # layer in front of it.
  # `activation/<token>` is included and is why the pattern has no trailing `$` —
  # it carries the token in the path, runs a DB query per call and returns the
  # invitee's email on a hit, and the app applies no throttle of its own there.
  # A route left out of this list is a route with no limit at all: the zone only
  # applies where a location names it.
  # Regex location (takes precedence over `location /`), so it repeats the proxy
  # setup; rejections give 429.
  location ~ ^/api/auth/(login|activate|forgot-password|confirm-email|activation/) {
    limit_req zone=kouizine_auth burst=5 nodelay;
    limit_req_status 429;

    proxy_pass http://kouizine_app;
    proxy_http_version 1.1;
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_redirect off;
  }

  # The only routes that upload anything: the recipe thumbnail
  # (KOUIZINE_MAX_IMAGE_MB, a raw body the device's file queue sends) and the
  # recipe movie (KOUIZINE_MAX_MOVIE_MB, 200 MB by default). The app enforces
  # the real per-kind cap itself (the file store's limit for the thumbnail, a
  # DefaultBodyLimit for the movie); this is only the ceiling above it.
  # `proxy_request_buffering off` streams the body straight through instead of
  # spooling the whole movie to the proxy's disk first. Uploads and removals
  # (PUT, DELETE) share the per-client kouizine_uploads bucket; the downloads
  # (GET, HEAD) are exempt.
  location ~ ^/api/recipes/[^/]+/(thumbnail|movie)$ {
    limit_req zone=kouizine_uploads burst=60 nodelay;
    limit_req_status 429;

    client_max_body_size 210m;
    proxy_request_buffering off;

    proxy_pass http://kouizine_app;
    proxy_http_version 1.1;
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_read_timeout 120s;
    proxy_send_timeout 120s;
  }

  # SSE liveness stream — long-lived by design, so it is capped per source IP
  # and must not be buffered (buffering would swallow the pings and the app
  # would call itself offline). 16: a normal browser's tab count with room for
  # a reload overlapping the stream it replaces; under HTTP/2 nginx counts each
  # concurrent request as a connection.
  location = /api/events {
    limit_conn kouizine_events 16;
    limit_conn_status 429;

    proxy_pass http://kouizine_app;
    proxy_http_version 1.1;
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_redirect off;
    proxy_buffering off;
    proxy_read_timeout 1h;
  }

  # SSE change stream (the platform's sync contract) — the same long-lived,
  # unbuffered treatment as the liveness stream (buffering would hold the
  # `sync` events until the connection closed, which is never), but
  # authenticated and on its own connection bucket. An exact-match location: it
  # would otherwise fall through to `location /` and be buffered there.
  location = /api/events/sync {
    limit_conn kouizine_sync_events 8;
    limit_conn_status 429;

    proxy_pass http://kouizine_app;
    proxy_http_version 1.1;
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_redirect off;
    proxy_buffering off;
    proxy_read_timeout 1h;
  }

  # The sync round trip (recipes + ingredients): up to 500 changes per
  # collection in one JSON body — the recipes a phone edited while offline — so
  # the vhost's 1 MB ceiling is not enough here. A 413 would count as a failed
  # round on the phone and keep its outbox waiting. The app allows the same
  # 8 MB (web.rs).
  location = /api/sync {
    client_max_body_size 8m;

    proxy_pass http://kouizine_app;
    proxy_http_version 1.1;
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_redirect off;
  }

  # Liveness probe — public because the UI seeds its status dot with it, but
  # every hit runs a DB query against a 5-connection pool, so it is rate-limited:
  # a flood would otherwise saturate the pool and stall real requests. The
  # container healthcheck probes the same route with HealthOnFailure=kill, so a
  # saturated pool means podman kills the container, Restart=on-failure brings it
  # back into the same flood, and after StartLimitBurst cycles the unit stays down.
  # Its own zone rather than the auth one it used to share — see that zone's
  # comment: the app's own offline probing was spending the login budget.
  location = /api/health {
    limit_req zone=kouizine_health burst=20 nodelay;
    limit_req_status 429;

    proxy_pass http://kouizine_app;
    proxy_http_version 1.1;
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_redirect off;
  }

  # reverse proxy
  location / {
    proxy_pass http://kouizine_app;

    # keep it HTTP/1.1
    proxy_http_version 1.1;

    # forwarded headers. proxy_params APPENDS to the client's own
    # X-Forwarded-For, so a caller can prepend whatever hops it likes; NGINX is
    # the edge here and there is no upstream chain worth keeping, so overwrite
    # it with the real peer and the app can never be handed a forged hop.
    include proxy_params;
    # Empty Connection header: keeps the pooled upstream connection alive.
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Port $server_port;

    # specific configuration
    proxy_read_timeout 120s;
    proxy_send_timeout 120s;
  }
}

# restart nginx
sudo nginx -t && sudo service nginx restart

Replace kouizine.domain.fr by the name of your website, and 10050 by HOST_PORT.

Activate HTTPS

To activate HTTPS protocol, follow the Let's Encrypt section.

First login — activate the admin account

The admin account is created pending on first start (from KOUIZINE_ADMIN_EMAIL).
There is no admin password in kouizine.env. To activate it:

  1. On first start, the server e-mails an activation link to KOUIZINE_ADMIN_EMAIL (SMTP must be reachable — startup aborts otherwise).
  2. Open the activation link from the e-mail, choose a password, and you are signed in.
  3. The link is single-use and expires after KOUIZINE_ACTIVATION_TTL_HOURS (72 h by default).

Accounts are invite-only — there is no self-registration. The admin invites further users the same way (activation link by e-mail); each user edits their own recipes, and optional TOTP 2FA can be enabled from the profile settings.

⬆️ Updating Kouizine

Kouizine deploys from a dev machine: ./deploy.ps1 builds the production image for the server's architecture, publishes it to the fleet registry, then pushes the commit: that order is the whole invariant.

That push fires the bare repo's hook, which calls podmanctl --deploy kouizine <short-sha>: it acknowledges the push, then deploys detached. Nothing is built here — it pulls <registry>/kouizine:<app sha>.<platform sha>, checks its revision labels against the commit just checked out and starts it; with nothing published it refuses before stopping anything. Follow a deploy with sudo tail -f /var/log/kouizine-deploy.log.

🚀 Deploying a change

From the app's clone on a dev machine, with the platform clone beside it:

git add -u && git commit -m "..."
./deploy.ps1

deploy.ps1 does everything in order: build → push the image → git push. Never push first — the hook would fire before the image exists and the deploy would be refused.

It refuses early rather than wasting a build when the tree is dirty or has diverged from the server. With nothing left to push it asks the app's /api/version what production runs: HEAD itself → it exits 3 (skipped); no answer → exit 3 marked unconfirmed, with the reason; another commit → it publishes the image the server is missing and exits 4, naming the podmanctl --deploy left to run there. After a push it waits until /api/version reports the new commit (-NoWait skips the wait).

🪝 One-time setup — hook and clone wiring

The deploy entry point is central and installed once for the whole fleet — see Podman — Push deploys for podmanctl --deploy and its single sudoers rule. Only the two steps below are per-repository.

# install into the bare repo's hooks/ — fires on every push
# ${SERVICE_NAME} expands now; the rest stays literal (\$…) for git to expand
sudo tee /media/ssd/git/podman/${SERVICE_NAME}.git/hooks/post-receive >/dev/null <<EOF
#!/bin/sh
set -eu
DEPLOY_BRANCH=refs/heads/master
while read -r oldrev newrev refname; do
  [ "\$refname" = "\$DEPLOY_BRANCH" ] || continue          # only the deploy branch
  sudo /usr/local/bin/podmanctl --deploy ${SERVICE_NAME} "\$(git rev-parse --short "\$newrev")" </dev/null
done
EOF
# normalize the hook ownership
sudo chown www-data:debian /media/ssd/git/podman/${SERVICE_NAME}.git/hooks/post-receive
sudo chmod 0750            /media/ssd/git/podman/${SERVICE_NAME}.git/hooks/post-receive

# git seeded hooks/ with executable *.sample files — inert, but strip the bit
sudo chmod -x /media/ssd/git/podman/${SERVICE_NAME}.git/hooks/*.sample

The commit comes from the just-pushed ref (the bare repo already holds it) and only names the deploy in its log. Nothing else is baked in: podmanctl derives the service directory, user, admin group, env file and log path from the name it is given.

# deploys pull non-interactively as root: pull from the co-located bare repo over a
# LOCAL path (the HTTPS origin needs a credential prompt + TTY, which a hook lacks)
git -C ${SERVICE_DIR} remote set-url origin /media/ssd/git/podman/${SERVICE_NAME}.git

# trust both repos for root so the root-run `git pull` doesn't refuse with
# "detected dubious ownership"; --system applies whatever HOME the hook runs with
sudo git config --system --add safe.directory ${SERVICE_DIR}
sudo git config --system --add safe.directory /media/ssd/git/podman/${SERVICE_NAME}.git

Without the local origin the pull dies with could not read Username for 'https://…'; without safe.directory it dies with detected dubious ownership. Either way the worker aborts before podmanctl --update and leaves the service running on its previous build.

🧱 Upgrading the base images

Every image the build starts FROM is pinned in kouizine.env — rust:${RUST_VERSION}-slim-trixie, node:${NODE_VERSION}-alpine, debian:${DEBIAN_TAG}, alongside the stack's postgres:${POSTGRES_VERSION}. The .build units pass them as --build-arg and build/Dockerfile carries matching ARG defaults, so nothing moves under the fleet on its own. Kouizine builds on a dev machine, so the bases are pulled there; here --upgrade still refreshes postgres:${POSTGRES_VERSION}. Refreshing is a deliberate step:

podmanctl --list --check            # UPDATE column shows when an upstream image moved
podmanctl --upgrade kouizine        # pull bases + registry images, then rebuild + restart

The env files are gitignored: add a new key on the server before the push that needs it, or a quadlet expanding ${RUST_VERSION} against a missing key builds rust:-slim-trixie and fails. A bumped RUST_VERSION invalidates the whole Rust layer chain — toolchain, every dependency crate (a fresh cargo cache) — so that rebuild runs 15 min+ on the ARM host: schedule it, don't treat it as a routine deploy. Edit and push a pin first (build/Dockerfile, kouizine.env, postgres.env), then --upgrade.

✅ Platform conformance

Kouizine consumes the shared platform — the platform-* crates and @platform/* packages its image is built from — so the platform's conformance suites must stay green for it. They run on the local stack only, never against production (2026-10-01): from the shared-core checkout, before every deploy,

./scripts/fleet-check.ps1 -Apps kouizine -UseVsClang

It starts run-local.ps1 -Detach -ResetDevAdmin, runs the HTTP suite, the browser suite and this app's own e2e/ through the stack's own nginx (https://127.0.0.1:8448), checks that nginx itself, then stops the stack. The whole fleet at once: Release & rollout — Fleet conformance.