Set of Boxstarter scripts leveraging on WinGet to setup my PCs/VMs for different applications. This is a conversion of the Chocolatey based repo https://github.com/microsoft/windows-dev-box-setup-scripts. The goal of this project is to install the majority of my needed software and tools for new machines (virtual or physical)
These scripts leverage these popular open source projects.
- Boxstarter boxstarter.org
- Winget []
- Chocolatey chocolatey.org (This is only used if Winget doesn't have a package and Chocolatey does)
The script code is organized in a hierarchy
Recipes A recipe is the script you run. It calls multiple helper scripts. These currently live in the root of the project (HomePC.ps1, etc.)
Helper Scripts: A helper script performs setup routines that may be useful by many recipes. Recipes call helper scripts (you don't run helper scripts directly). The helper scripts live in the scripts folder
Note: The one-click links use the following format. When working out of a different Fork or Branch you'll want to update the links as follows:
To run a recipe script, click a link in the table below from your target machine. This will download the Boxstarter one-click application, and prompt you for Boxstarter to run with Administrator privileges (which it needs to do its job). Clicking yes in this dialog will cause the recipe to begin. You can then leave the job unattended and come back when it's finished.
Before clicking on one of these links, you may need to enable running scripts in Powershell. This is done by running the following code:
Set-ExecutionPolicy Unrestricted
Also had to upgrade winget...
Update the line for Python in CommonDevTools.ps1
After this completes you should reverse this by running:
Set-ExecutionPolicy Restricted
| Click link to run | Description |
|---|---|
| CloudEngDevPC | Sets up a cloud hosted PC to be a development environment for engineering, including essential tools and configurations. |
| HomePC | Sets up a home PC with preferred software and utilities for general use. |
Notes:
- If you are using WSL there's a followup step we recommend after running the setup script. When the script finishes you will only have a root user with a blank password. You should manually create a non-root user via
$ sudo adduser [USERNAME] sudowith a non-blank password. Use this user going forward. For more info on WSL please refer to the documentation. - If you're a Node.js contributor working on Node.js core, please see the Node.js Bootstrapping Guide or click here to run.
- The Boxstarter ClickOnce installer does not work when using Chrome. This issue is being tracked here. Please use Edge to run the ClickOnce installer.
- Reboot is not always logging you back in to resume the script. This is being tracked here. The workaround is to login manually and the script will continue running.
- There have been reports of Windows 1803 not successfully launching Boxstarter via the web launcher. See this issue for details: chocolatey/boxstarter#301