Problem
Current Forkana compose deployments need better operational defaults and more flexibility for non-default environments.
Logs can grow indefinitely without explicit rotation settings, which risks disk pressure in long-running environments. At the same time, the default stack assumes a bundled Postgres service, which makes it awkward to run Forkana against an existing external Postgres instance.
These scenarios are currently possible, but changing logging drivers or using an external database is error-prone when compose files are layered inconsistently. Operator guidance for these setups is also fragmented.
Solution
Introduce compose-level defaults, optional overrides, and clearer operator documentation.
Problem
Current Forkana compose deployments need better operational defaults and more flexibility for non-default environments.
Logs can grow indefinitely without explicit rotation settings, which risks disk pressure in long-running environments. At the same time, the default stack assumes a bundled Postgres service, which makes it awkward to run Forkana against an existing external Postgres instance.
These scenarios are currently possible, but changing logging drivers or using an external database is error-prone when compose files are layered inconsistently. Operator guidance for these setups is also fragmented.
Solution
Introduce compose-level defaults, optional overrides, and clearer operator documentation.