Exposure Strategy
Use to decide how a service should be reachable - external public HTTPS via subdomain, internal Basic-Auth-protected HTTPS, sharing a subdomain via path rule, root subdomain, or not exposed at all.
Use to decide how a service should be reachable - external public HTTPS via subdomain, internal Basic-Auth-protected HTTPS, sharing a subdomain via path rule, root subdomain, or not exposed at all.
Use to decide whether a template should be a long-running HTTP service, a one-shot job (Trick) with `job_watch`, a scheduled job via `schedule_config`, or a VCS-triggered job via `trigger_config`.
Use to decide where a credential or secret-like value belongs - template variable (with optional `random`/`secret`/`sensitive`), Fibe Secrets, or Job ENV - and how to wire it.
Use when classifying a Compose service as a Fibe static (prebuilt image) or dynamic (source-backed - cloned/built/mounted from a Git repository) service.
Use to decide whether to enable `fibe.gg/zerodowntime` on a service - the prerequisites, what to remove, optional healthcheck tuning labels, and when NOT to enable it.