{"id":252,"date":"2022-06-10T21:20:00","date_gmt":"2022-06-11T02:20:00","guid":{"rendered":"http:\/\/sycured.127.0.0.1.sslip.io\/?p=252"},"modified":"2024-01-14T11:58:35","modified_gmt":"2024-01-14T16:58:35","slug":"azure-app-services-web-apps-config-versioning","status":"publish","type":"post","link":"http:\/\/10.42.0.68:8080\/blog\/azure-app-services-web-apps-config-versioning","title":{"rendered":"Azure App Services Web Apps Configuration – Versioning"},"content":{"rendered":"\n

Working with Azure App Services Web Apps, I learned how it is to not have integrated versioning of the configuration.<\/p>\n\n\n\n

This is my solution.<\/p>\n\n\n\n\n\n\n\n

My setup<\/h2>\n\n\n\n

It’s always better to have a distributed system that requests\/processes everything in parallel.<\/p>\n\n\n\n

Nomad<\/a> has the parameterized job type, it’s one of my actual tools for this versioning.<\/p>\n\n\n\n

I can run any command specifying parameters like the ones that I use:<\/p>\n\n\n\n