Script directory for a PowerShell profile.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
lksz 4da3726760 Some modifications 4 days ago
7zip Fixes 3 weeks ago
GitHub Improvements and bug fixes 2 weeks ago
ansible Updated Pull-ViaAnsible to allow Path 1 month ago
base Some modifications 4 days ago
base.linux Module loading upgrade 1 week ago Fixes to packagesz class code and the win package 2 months ago
docker Some modifications 4 days ago
scoop Moved logic to szcoop repo 2 weeks ago
shell-loading-snippets Some modifications 4 days ago
.gitignore updated .gitignore 1 month ago
LICENSE Initial commit 5 months ago Introducing Packages 3 months ago
Setup-Profile.ps1 Modify Setup, Path, added Get-MyModules 1 week ago

PowerShell Scripts

These are the scripts that go into $MyPSScriptRoot which is part of my $env:PATH.

The development of these is documented in my blog:

They are provided ‘as is’ for your review and for your reuse.

This envrionment can be installed using one the following options:

The Short, yet safer way

iwr | iex

This sets up the $PROFILE file, and initilizes the default dir $MyPSScriptRoot with a git clone of this repo. The actually points to the Setup-Profile.ps1 script, which means, that after you have the Scripts directory setup, you can call Setup-Profile to update the $PROFILE after the Setup-Profile.ps1 has been modified (or updated via git pull).

The somewhat Short, but with control option

$sfw=1; iwr | iex; _setup [-sudo] [-Force] [-NoGitClone] [-GitURL <alternative git URL>] [-WhatIf] [-Confirm] [<CommonParameters>]

The key here is $sfw=1, which can be substitued with the more verbose $SetupFromWeb=1, this let’s the Setup-Profile script know to just load it’s content, but allow you to manually call it’s internal function via _setup

The ‘I don’t trust one liners, what’s going on ?!?’ option

You can always clone the git repo first, and only then run the Setup-Profile.ps1 script.