Summary:
Add a dedicated disable_ui configuration option that disables the Web UI while keeping the REST API fully operational.
Problem:
The current disable_web flag disables both the Web UI and the REST API together. This makes it impossible to run backman in a headless/API-only mode. When backman is used exclusively via its REST API (e.g. in CI/CD pipelines), the UI serves no purpose and unnecessarily increases the attack surface.
Proposed Solution:
Introduce a new disable_ui boolean config option that, when set to true, skips registration of the Web UI routes and renderer while keeping the API routes active.
Use Case:
Running backman on Cloud Foundry where the REST API is consumed by deployment pipelines but the Web UI is not needed and should not be publicly accessible.
Summary:
Add a dedicated disable_ui configuration option that disables the Web UI while keeping the REST API fully operational.
Problem:
The current disable_web flag disables both the Web UI and the REST API together. This makes it impossible to run backman in a headless/API-only mode. When backman is used exclusively via its REST API (e.g. in CI/CD pipelines), the UI serves no purpose and unnecessarily increases the attack surface.
Proposed Solution:
Introduce a new disable_ui boolean config option that, when set to true, skips registration of the Web UI routes and renderer while keeping the API routes active.
Use Case:
Running backman on Cloud Foundry where the REST API is consumed by deployment pipelines but the Web UI is not needed and should not be publicly accessible.