Hello and thanx for your wonderfull tool :)
I have build a docker image with a gui inside webbrowser for ROMVault, based on older work.
see https://github.com/StudioEtrange/docker-romvault
In a web browser it works perfectly and looks like :

For a good automation process, could you publish your binary in a predictable url and browsable url ?
as I can build docker images with same version tag than romvault versions
For example :
https://www.romvault.com/download/: list all avaible version so we can choose older version to rebuild any previous docker image
https://www.romvault.com/download/latest : download romvault.3.4.1.zip
https://www.romvault.com/download/romvault.3.4.0.zip : download romvault.3.4.0.zip
...
https://www.romvault.com/download/romvault.3.2.2.zip : download romvault.3.2.2.zip
...
On your website romvault.com or If you wish on github release
you could publish all your versions in release tab of github, so we can interact with github to retrieve a specific version or the latest.
Thank you !
Hello and thanx for your wonderfull tool :)
I have build a docker image with a gui inside webbrowser for ROMVault, based on older work.
see https://github.com/StudioEtrange/docker-romvault
In a web browser it works perfectly and looks like :

For a good automation process, could you publish your binary in a predictable url and browsable url ?
as I can build docker images with same version tag than romvault versions
For example :
https://www.romvault.com/download/: list all avaible version so we can choose older version to rebuild any previous docker image
https://www.romvault.com/download/latest : download romvault.3.4.1.zip
https://www.romvault.com/download/romvault.3.4.0.zip : download romvault.3.4.0.zip
...
https://www.romvault.com/download/romvault.3.2.2.zip : download romvault.3.2.2.zip
...
On your website romvault.com or If you wish on github release
you could publish all your versions in release tab of github, so we can interact with github to retrieve a specific version or the latest.
Thank you !