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
Pass a path to CMPackager.ps1 to look for recipes, extra files, and the preference file. This would allow people to manage their own recipes and preferences outside of this repo.
Use cases:
Recipes may contain sensitive data and cannot be shared
Using installer/uninstaller scripts instead of direct commands in the deployment types
In general it might be a better idea to completely split out the recipes, but that is a much bigger undertaking.
The text was updated successfully, but these errors were encountered:
So what I do now, is exclude the recipes folder using .gitignore, so you can always keep the packager up-to-date, but not have any of your recipes shared/messed up with git. Does this not fit your situation?
Pass a path to CMPackager.ps1 to look for recipes, extra files, and the preference file. This would allow people to manage their own recipes and preferences outside of this repo.
Use cases:
In general it might be a better idea to completely split out the recipes, but that is a much bigger undertaking.
The text was updated successfully, but these errors were encountered: