box o' scripts in Batch, PowerShell, and Unix (for WSL)
Recommended Install: Add folder(s) to PATH
- What is Windows PATH and How Do You Add to and Edit it? - Make Tech Easier
- Save scripts to the folder(s) you added to your PATH
- You can now run the script from anywhere with just the name (ie:
ff-u
) - The folders I have in my PATH are
appscmd
andmodscmd
Local Install: Run in one folder only
- Open the folder you saved the scripts to (in Windows Explorer)
- Click the address bar (The long box with the folder path)
- Type
cmd
orpowershell
and hit enter - In the console window that pops up, you can run the script
powershell
scripts need to start with.\
and end with.ps1
(ex:.\Script.ps1 -Param 'Arg'
)
- Keep in mind that running the script from another folder is only possible with relative or absolute paths (ie:
C:\scripts\ffmpeg\ff-u
instead of justff-u
)
- Each script has its own prerequisites
- PowerShell scripts (
.ps1
) require PowerShell on Windows (you probably already have this; check withpowershell
in a cmd window) - Batch scripts (
.bat
) require cmd on Windows (all Windows versions have this; typecmd
in start menu, or in address bar of Windows Explorer) - UNIX scripts (
.sh
or no extension) require WSL on Windows or a Linux OS
- add readme for all scripts
- GetHub.ps1: add pre-releases
Written with StackEdit.