How about using this tool as PaaS offering #67
amitjattan
started this conversation in
Ideas
Replies: 1 comment 15 replies
-
Hi @amitjattan, this is a great question! If a customer deploys the standard offering, the containers are hosted in a public Azure Container Registry. As the containers are updated, the only thing users have to do is simply restart the App Service, and the new containers will be pulled down. In the near future, I'll probably add in some automation around this restart so it "just happens". If a customer chooses to deploy this solution in a Private ACR, then they will need to pull down the updated code from GitHub and build the new containers into their ACR's on a regular basis. Did that help to answer your question completely? |
Beta Was this translation helpful? Give feedback.
15 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@msftgits @DCMattyG Looks like currently tool is deployed as owned solution by customer and it's hard to accommodate new features in the tool when added in this repository, how do you suggests consumers to update tool once deployed in their environments?
Beta Was this translation helpful? Give feedback.
All reactions