Config scheduledTasks across multiple environments
What is the best way to configure a scheduled task so it will run in whichever environment the website is published to?
I would like to check in a version that works for the DEV environment but I don't want the umbracoSettings.config to be overridden in STAGE by this version when I publish.
Today, we manually publish from VS2015 but next year our plan is to publish in a more automated fashion with a CI/CD pipeline. So although I could manually change it in each environment and update the url to be specific to each environment I don't want to do it manually.
I'm trying to determine how best to solve it for today but with an eye for the future when we have it more automated.
Here is an example of the scheduledTask I am using today:
Config scheduledTasks across multiple environments
What is the best way to configure a scheduled task so it will run in whichever environment the website is published to?
I would like to check in a version that works for the DEV environment but I don't want the
umbracoSettings.config
to be overridden in STAGE by this version when I publish.Today, we manually publish from VS2015 but next year our plan is to publish in a more automated fashion with a CI/CD pipeline. So although I could manually change it in each environment and update the url to be specific to each environment I don't want to do it manually.
I'm trying to determine how best to solve it for today but with an eye for the future when we have it more automated.
Here is an example of the scheduledTask I am using today:
I would like to either use relative paths for the URLs or replace
localhost:62891
with a token that is replaced for each environment.Thoughts?
Hi Paul,
We use config transforms for this using the Slow Cheetah plugin for visual studio.
You will need to have different build configs for all your environments.
So when you build for Live, the live transform will be applied to the config file.
dave
is working on a reply...