Hypothetically, you could. Someone with devops expertise just needs to modify a few of the dependencies in the script that gets executed on the Azure VM in order to create a production environment that is suitable for the v0.8.x release. And then someone else needs to test the heck out of the feature.
The original author of the Deploy to Azure button is no longer working on OpenBoxes so we don’t have anyone (other than myself) to support this feature. I can certainly investigate when I get a chance but I can’t promise anything at the moment given my capacity as a paid consultant.
A Little Backstory
The Deploy to Azure feature was part of a larger “Shelf Readiness” project funded by Digital Square in 2020.
The hope was that once the Deploy to Azure feature was working, we’d also be close to releasing OpenBoxes v0.9.0 (which would include a large migration from Grails 1 to Grails 3). I wanted to future-proof the Azure deployment process so we didn’t have to migrate the Deploy to Azure feature once we were done with v0.9.0.
Unfortunately, we didn’t anticipate how long it would take to get the Grails 3 migration funded. After a three-year hiatus, we finally restarted the project in May 2023 and we are hoping to be done in the Fall 2023.
As with everything open-source we either have to find funding for the work we want to do or find someone willing to work for free. I do a little of both, but priority usually goes to the work being funded.