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.
Gal Szkolnik 624ca2cc8c =added option to stay around after pwsh 1 week ago
7zip =Added comment to convertto-zip for clarity 1 month ago
HomeAssistant Add support for preserving specific devices 1 week ago
ansible Ansible Output improvements 2 months ago
base Added better constrol over waiting for editor 1 week ago
base.linux Improve performance of Package identification 2 months ago Added Get-EventLogSz (after pulling upstream) 2 months ago
docker Fix dps and Get-HAPath 1 week ago
git Add -UseBasicParsing to bypass warning in Windowsi 2 months ago
hastebin Added haste module with New-Haste cmdlet 2 months ago
scoop scoop package support for [SessionData] 3 weeks ago
shell-loading-snippets =added option to stay around after pwsh 1 week ago
.gitignore Added Pause and RandomString + some minor fixes 3 months ago
LICENSE Initial commit 10 months ago updated after renaming the setup script 1 month ago
Setup-ScriptEnv.ps1 =Fix SessionData Get bug when persistent storage doesn't exist yet 3 weeks 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 is the way

Below are instrucitons for initializing/setting up this envrionment:

iwr | iex
_Init # [-WriteInitScript] [-sudo] [-Force] [-NoGitClone] [-GitURL <alternative git URL>] [-WhatIf] [-Confirm] [<CommonParameters>]

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-ScriptEnv.ps1 script, which means, that after you have the Scripts directory setup, you can call Setup-ScriptEnv -WriteInitScript to update the $PROFILE after the setup script has been modified (or updated via git pull).