Azure Oqtane/Module update without downtime #4973
Replies: 2 comments
-
Not sure if this is adaptable for Azure, but I store a lot of images for one of my Oqtane sites outside of the Oqtane content folders for this exact reason. My content is for public use, so there isn't any security around being able to link to the images, so this may or may not work for you. Inside my appsettings.json, I set values for where the files are physically stored and what virtual folder they will appear as within the Oqtane site. Then, within the ServerStartup.cs file of my module, I create the mapping to use that location. [appsettings.json file]
[ServerStartup.cs file]
|
Beta Was this translation helpful? Give feedback.
-
@mdmontesinos the concept of "folder providers" has been discussed previously as part of a larger "scale out" enhancement @W6HBR thank you for sharing... the native FileProvider capability in .NET Core is very powerful |
Beta Was this translation helpful? Give feedback.
-
Has anyone been able to upgrade the Oqtane version or update a module in Azure App Service without having downtime for the site?
For regular Blazor apps, I've used Deployment Slots so that I can deploy the new code to a staging slot and, when tested, swap it with the production one with zero downtime.
However, this approach does not work for Oqtane because it relies in the files in the Content folder, which are not shared between slots. You would need to manually copy all new files between slots before each swap. Perhaps if Oqtane supported Azure File Storage it'd be easier to handle the files in a central location.
Are there any other ways to achieve zero downtime on updates?
Beta Was this translation helpful? Give feedback.
All reactions