-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass in user settings via command line #42
Comments
Nice! This one would have been my second pick to be resolved! |
You can now pass in the Web Deploy parameters as a command line parameter. How to use with a PublishConfiguration.ps1If you are using a PublishConfiguraiton.ps1 you can just add the parameters to the end of the call to
If a parameter exists in both PublishConfiguraiton.ps1 as well as the command line, the command line value wins. How to use without a PublishConfiguration.ps1If you want to pass in all the Web Deploy parameters, and not use a PublishConfiguration.ps1 file then you need to additionally pass in the
I have a drop for testing available at https://dl.dropbox.com/u/40134810/PackageWeb/issue-42/PackageWeb.1.1.8.11.zip. |
Excellent! Does it matter if I use single or double quotes when entering params on the command line? |
It shouldn't matter but they have different behavior in PowerShell. If you are not familiar with that I'd suggest you to look it up. |
Note that this seems to be broken in the latest version - the workaround is to have a dummy PublishConfiguration.ps1 file and still specify your commands, so it looks something like;
|
Currently all publishing settings are gathered from a .ps1 file. This makes it difficult to automate publishing to many environments.
We should be able to pass in specific parameters through the command line. This should be additive to the PublishConfiguration.ps1 file. When specific parameters are passed in they should take precedence over those found in the PublishConfiguration.ps1.
The text was updated successfully, but these errors were encountered: