Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd -ModulesFolder command line argument to the Client #26
Labels
Comments
|
Sounds like a good idea to me and if the DeployClient is proving useful to people off the shelf then the added flexibility will be appreciated I'm sure. |
HaGGi13
added a commit
to HaGGi13/PolyDeploy
that referenced
this issue
Jun 7, 2020
Introduced PackagesCrawler to encapsulate logic that will read all installation packages full file paths. It enables the DeployClient to read installation packages from a defined directory. It's no more necessary to save installation packages beside the DeployClient.exe. Encapsulated code in own method, that will write packages information to console and cancels the execution if no packages were found in packages directory, to get better readable code. Added unit tests for new PackagesCrawler component. Migrated Solution to Visual Studio 2019. Updated DeployClient project to .Net Framework 4.8 to get it up to date. Related issue: cantarus#26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the client looks at the Current Directory, but it would be a nice feature to have, to be able to specify where the module zips are located on disk via cmd argument.