Docs: Clearer DNS instructions and cross-linking

[joepavitt]

Description

We're losing an estimated 93% of traffic to the first step in our self-hosted install instructions for our "Quick Start" guide. This attempts to remedy the step/intimidation of setting up a DNS server in Step 1, which will hopefully improve conversion here.

[ppawlowski]

Technically it looks fine.
However, this increases the complexity of quick-start documentation and the whole setup process. Not quite convinced about this change.

You can merge it whenever you feel it's ready to be made publicly available.

[joepavitt]

However, this increases the complexity of quick-start documentation and the whole setup process. Not quite convinced about this change.

How does it though? Currently, step 1 is setup a DNS server and get yourself a domain, which is a big step putting off 93% of visitors... the plan here is to provide the non-DNS route for quicker onboarding?

I'd even go as far as saying bin DNS option in quick start entirely, and just present the non-DNS option

[ppawlowski]

The current approach requires one to have a Fully Qualified Domain Name with the possibility to modify its DNS records. It does not require to setup a DNS server.
No-DNS approach requires one to use an external service and the way this service works might lead users to questions like: Which IP address should I put there? How can I check what is my IP?
Alternatively, if they cannot afford an FQDN, they can still use FlowFuse Cloud to evaluate the product. Maybe we should put a link to the FFC registration page?

I might be wrong, but I feel that we might not benefit much from this change. On the other hand, given the high failure rate, we probably won’t lose much either.

[hardillb]

@joepavitt Can we publish this?