I’m curious if anyone runs Windows not as the Local Administrator (possibly in a corporate environment where the user isn’t the main admin on the PC) and noticed issues with deploying to remote servers using Wappler’s Resource Manager?
At times you need to run Wappler as the administrator for actions like creating a local project with a docker container and then subsequently trying to deploy using the Resource Manager. If you were not running Wappler as administrator initially then the ssh key would be created in the current user’s directory, but if you then restart Wappler using “run as administrator”, then Wappler looks for the ssh key in the administrator’s document directory instead of the current user’s directory.
I’m not sure if this would cause issues when deploying to remote resources created in the Resource Manager, but I saw some strange issues on another Wappler’s system and trying to understand if this is an issue for others.