PPawlowski

@joepavitt All are valid, however: * DNS setup is required due to the nature of our application (web service) * TLS and SMTP configuration are optional and not required for...

Actually, when talking about things a customer _could_ need to set up - database is something which needs to be added to the list. For both Docker and Kubernetes approaches...

Quick Start: * Required: dedicated domain (DNS setup) * Optional: TLS, SMTP, external database Production: * Required: dedicated domain (DNS setup) * Recommended: external database, TLS * Optional: SMTP A...

There is a possibility to configure FlowFuse **core app** to run on localhost. However, running **Node-RED instances** won't be possible. They are scheduled to run on the subdomain of the...

The checklist has been defined and implemented in our documentation.

I'm not sure if anything has been done in this area, but I no longer experience the described error. Safari version: `18.5 (20621.2.5.11.8)` macOS version: `15.5 (24F74)` Node-RED Version: `4.0.8`...

After another review it turns out, that the problem exists on FFC production environment only. The following error has been observed in the browser's console while accessing the editor: ```...

> FFC customers receive a message in their Notifications Hub upon each release. This is a part of the Release Checklist. That's exactly what happens currently. > SH customers can...

While a central notification hub, where a single message about the availability of a new FlowFuse version can be created, sounds like a nice idea, this should work in a...

I agree with @cstns - while having global 'enable all features' looks like a quick win, we should somehow handle features that require additional configuration before enabling (like AI stuff...