[ARGO] Legacy cloudflared configuration

I am very happy with the operation of ARGO using the cloudflared installation and I do not want to migrate - I not that my configuration is flagged as legacy but I want to keep it the same because it is scriptable without having to SED an existing configuration file if adding new websites but,

If I presently have multiple cloudflared instances running each their own configuration file on the same server, what is the correct instruction of the config.yml file, is there an example? – Currently the cloudflared service registers its own subdomain and that is an !IMPORTANT feature for scriptable server configuration otherwise the CloudFlare API has to be scripted and that is FBS as far as I am concerned when the cloudflared service can do it.

Here are the instructions I followed:

1 Like