The platform keeps moving: five new templates and smarter env refs

Most of our recent posts were about Kaisen, but the platform moved too. Today we added five one-click templates (Miniflux, Forgejo, Wiki.js 2, Memos, Vaultwarden), env values with several refs, and a mounted database CA.

Share

Most of our recent posts were about Kaisen. The platform kept moving too. Today we shipped five new one-click templates and two changes to how env vars and the database CA work. Every template was tested live on a throwaway app first.

Five new templates

  • Miniflux (RSS reader, Postgres). The public image runs unchanged. About 21 MiB RAM. Limit: no email.
  • Forgejo (git forge, 1 GiB volume). The public rootless image runs unchanged. About 98 MiB RAM. Limit: git over HTTPS only, no SSH, no Actions.
  • Wiki.js 2 (wiki, Postgres). The public image runs unchanged. About 45 MiB idle, 143 MiB peak. Limit: an admin must raise the app's DB connections to 10, or saving a page fails.
  • Memos (notes, Postgres). About 24 MiB RAM. Limit: attachments live in the 50 MB database unless you set up S3.
  • Vaultwarden (Bitwarden-compatible server, volume). About 29 MiB RAM. Limit: no email, so no invites or email 2FA. Keep only passwords you can afford to lose.

Memos and Vaultwarden need a one-line wrapper image. Upstream runs as root, and we reject root images. The wrapper is FROM upstream plus USER 10001:10001. Nothing else changes.

For Forgejo, Memos and Vaultwarden, the first account to sign up is the admin. Register right away, then close sign-ups.

What the recipes taught the platform

Building these showed us two gaps, so we fixed them.

Env values can mix text and refs. A value can now hold plain text and several ${{ }} refs. Substitution is a single pass, so a resolved value is never expanded again. This lets you build a DSN from parts:

DATABASE_URL=postgres://${{ db.user }}:${{ db.password }}@${{ db.host }}:${{ db.port }}/${{ db.name }}?sslmode=verify-full&sslrootcert=${{ db.ca_file }}

The database CA is a file. Apps with a database now get the CA at /etc/picopaas/db-ca.pem, with a ${{ db.ca_file }} ref for the path. Miniflux, Memos and Forgejo now use verify-full. We checked that it is really used: pointing it at the system bundle fails with "certificate signed by unknown authority". For apps that want the certificate text, like Wiki.js, there is ${{ db.ca_cert_body }}.

One new guardrail: env values are capped at 8 KiB.

What's next

Linkding and Uptime Kuma still need wrapper images before they can ship.