Configuring a greffon
Each greffon exposes its settings as a form. You fill in values; Greffon writes them where the app expects them and handles TLS and routing.
Schema-driven forms
A greffon version declares its configuration options. Greffon renders them as a form — no YAML editing. You set values like an admin email or a database password and graft.
Where values go
Each option lands in one of three places, depending on what the app needs:
- Environment variable — injected into a service’s environment (e.g.
DB_PASS). - Config file — written as JSON into a named volume the app reads from.
- File upload — a file you provide, written into a volume (certificates, custom configs).
Ports, URLs & TLS
You don’t map ports by hand. The greffer allocates a host port, puts an Nginx reverse proxy in front of each instance, and terminates TLS — so every greffon gets an HTTPS URL automatically.
Automatic TLS
Certificates are issued by Greffon’s built-in certificate authority and installed on the greffer for you. There’s nothing to renew by hand.