You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.
How to specify different config file as command line argument when publishing to different environments. Currently only a verbatim string can be specified, This is critical for publishing the config file based on different environment as it have different certs and keys based on environment.
In the example below the config file is specified as hardcoded value, is it possible to supply a parameter or variable ?
<EntryPoint>
<ExeHost>
<Program>traefik.exe</Program>
<Arguments>--configfile=traefik.toml</Arguments>
<WorkingFolder>CodePackage</WorkingFolder>
<!-- Uncomment to log console output (both stdout and stderr) to one of the
service's working directories. -->
<ConsoleRedirection FileRetentionCount="5" FileMaxSizeInKb="2048" />
</ExeHost>
</EntryPoint>
The text was updated successfully, but these errors were encountered:
You can try out #65. The code might need some cleanup but it is supposed to help in the scenarios you are talking about. It lets you fetch certs from machine or KeyVault and then drop them with a specific name.
We want to be able to define environment specific configuration to Traefik via env vars to enable greater flexibility and we have an outstanding here: containous/staert#42 written by @serbrech to start this process but it is slow going!
How to specify different config file as command line argument when publishing to different environments. Currently only a verbatim string can be specified, This is critical for publishing the config file based on different environment as it have different certs and keys based on environment.
In the example below the config file is specified as hardcoded value, is it possible to supply a parameter or variable ?
The text was updated successfully, but these errors were encountered: