Go to file

lksz (@amnon) 8b2a4ca0cb Tweaks and fixes Improved sz-df output of zfs mounts Removed PowerShellCookbook dependecy in Packagesz class		2020-12-02 00:00:57 -05:00
base	Tweaks and fixes	2020-12-02 00:00:57 -05:00
base.linux	Tweaks and fixes	2020-12-02 00:00:57 -05:00
base.win	Introducing Packages	2020-11-25 01:20:52 -05:00
docker	Introducing Packages	2020-11-25 01:20:52 -05:00
shell-loading-snippets	Streamlined pwsz loading from Linux shells	2020-12-01 23:31:42 -05:00
.gitignore	Setup-Profile and co.	2020-09-25 01:30:21 -04:00
LICENSE	Initial commit	2020-09-16 10:56:03 -04:00
README.md	Introducing Packages	2020-11-25 01:20:52 -05:00

README.md

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: https://blog.lksz.me

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 https://lksz.me/pwsz | iex

This sets up the $PROFILE file, and initilizes the default dir $MyPSScriptRoot with a git clone of this repo. The https://lksz.me/pwsz 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 https://lksz.me/pwsz | 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.