[Feature Request]: Sing Cloud Server as Master and Another Instance as Worker (Same Network)

[KarlaVirtual]

Is there an existing feature request for this?

• I have searched the existing issues

What is your feature request?

Hello,

I currently have two cloud-based instances running within the same private network.

• One instance is already configured as the master (primary) Cronicle server.
• The master is fully functional and accessible via the web interface.
• The second instance is intended to act as a worker (slave) node.
  However, I have been unable to successfully connect the worker to the master, even after installing Cronicle correctly on both servers.

What I Have Done
- Cronicle is installed and running on both instances.
- The master server works correctly via the web UI.
- The worker starts without errors and waits for a master connection.
- Both servers are in the same network segment and can reach each other at the OS/network level.
- Firewall rules have been reviewed and adjusted.
- I followed the existing documentation, but only partially, as there is no clear or complete guide for this specific scenario.

Problem
There is no clear documentation explaining how to properly configure:
- A cloud-based master
- With another cloud instance as a worker
- Especially when broadcast discovery does not work or is restricted (common in cloud environments)

From the web interface, the worker never appears or connects, even though Cronicle is installed and running.
Request

I would like to ask:

- Is there an official or recommended way to connect a worker to a master without relying on UDP broadcast?
- Are there specific required configuration fields (master_hostname, server_comm_port, etc.) that must be set  for cloud environments?
- Could the documentation be expanded to include:
- Cloud-to-cloud setups
- Master/worker configuration without broadcast
- Common pitfalls (firewall, ports, roles)

I believe this is a common real-world use case, and clearer documentation would be very helpful for users deploying Cronicle in cloud infrastructures.

Code of Conduct

• I agree to follow this project's Code of Conduct