Misc changes to automate certain steps and docs #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Note that users often struggle with this step, since it either fails to them due to missing admin rights or not following steps properly. Therefore and to ease the initial process, we can install these modules without admin permissions if we install it to the current user scope. That way in the initial run it will install them automatically so we can reduce the steps from the readme.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is due to @xGuTeK's PR here: #31
I learned that if we set the scope to current user when installing powershell modules, there is no need for admin rights.
This means we can automate certain steps that beginners often struggle with and also to get started quickly with the project.
The main ko project config script will set the execution policy to bypass, so less users should struggle now with some of these steps.
Also improve the check for MSSQL installation, to first check if it is even installed before checking for SQL Instances.