Despite TLS_ENABLED set to `false`, application was configured with `https` in `base_url`

[ppawlowski]

Current Behavior

With the latest docker-compose file and default .env file, where TLS_ENABLED=false , the application was configured with base_url which included the https scheme.

Expected Behavior

If TLS_ENABLED is set to false, application should be configured with http scheme.

Steps To Reproduce

• Proceed with official FlowFuse Platform deployment using the Docker Compose
• ensure that in the .env file the TLS_ENABLED variable is set to false
• once deployed, check the value of base_url configuration parameter - it should contain http scheme

Environment

• FlowFuse version: 2.26.0
• Node.js version:
• npm version:
• Platform/OS: Docker
• Browser:

Linked Customers

https://app-eu1.hubspot.com/help-desk/26586079/view/233410279/ticket/353539377353/thread/16420713709#email

[ppawlowski]

With bash-style parameter expansion, if TLS_ENABLED is set and non-empty, the s is inserted into the base_url value regardless of the value. The false value still counts as “set”, producing https.
Since Docker Compose doesn’t support direct string comparisons in interpolation, there is no way to validate/use a value defined in any environmental variable.