You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have a CMD utility where I specify a folder, and the utility watches the folder indefinitely or until I stop it.
When a Module zip is dropped into the folder, the CMD utility uploads the zips via the DeployClient.
If it installs successfully, it's moved into a subfolder "Deployed", otherwise it goes in a subfolder "Failed".
I don't think this should be part of the DeployClient, but a separate cmd utility that interacts with the DeployClient.
If there's no interest to incorporate it into the PolyDeploy repo, I can create a separate repo to develop it for myself.
The text was updated successfully, but these errors were encountered:
For me the appeal is that I can just drop a zip into the folder manually, or as part of my Visual Studio build process to automate the Module Deployments. I see this as a local dev tool, but I don't think its useful for CI/CD systems, or for dev/staging/prod environments
I'd like to have a CMD utility where I specify a folder, and the utility watches the folder indefinitely or until I stop it.
When a Module zip is dropped into the folder, the CMD utility uploads the zips via the DeployClient.
If it installs successfully, it's moved into a subfolder "Deployed", otherwise it goes in a subfolder "Failed".
I don't think this should be part of the DeployClient, but a separate cmd utility that interacts with the DeployClient.
If there's no interest to incorporate it into the PolyDeploy repo, I can create a separate repo to develop it for myself.
The text was updated successfully, but these errors were encountered: