[Feature request] Fetch remco.toml and src template files from URL and be watchable

[rockandska]

Hi,

Thanks for your tool that seems interesting and promising.

Not sure if it is relevant, but i think it will be a great feature to have the possibility to fetch the template file from an public/private URL and be watchable with interval the same manner as values from backend.
I thinking it will be a perfect feature for remco.toml too (with autoreload and delete config files that are not here anymore)

I ask this because i'm looking for a solution to be able to distribute containers with defaults templates in image but to be able to fetch remco.toml/resources templates from URL/GIT.

What do you think ?

Regards,

[HeavyHorst]

I think you could try to put your remco.toml and template data into one of the supported backends (could be a yaml file on github or any other url) and then let remco rebuild its own config files and reload itself.

remco can write its pid to a file.
You could then reload with a command like: kill -HUP `cat /path/to/pidfile`

[HeavyHorst]

@rockandska does this work for you ?

[rockandska]

Sorry for the late answer.
Didn't try it yet but for now, my brain can't figure how to simply achieve this just by read the docs :)

Will it require at least 2 files by ressource template ?

• a remote yaml with a key containing the real toml
• a local resource template who just print the value of the toml placed inside a key on the remote yaml file

If you have an functional exemple, i'm open to read it :)

Thanks

[HeavyHorst]

Yeah, that's basically what I had in mind.

At the moment I don't have an functional example, but maybe I'll come up with one at the weekend.
If you're faster, feel free to post yours here.