Repeatable, reboot resilient windows environment installations made easy using Chocolatey packages
APACHE-2.0 License
Repeatable, reboot resilient windows environment installations made easy using Chocolatey packages.
For more information and How Tos, visit the official Boxstarter website.
The source of the Boxstarter website can be found in the boxstarter.org repository.
Import-Module Boxstarter.Chocolatey
New-BoxstarterPackage HelloWorld
Set-Content (Join-Path $Boxstarter.LocalRepo "HelloWorld\Tools\ChocolateyInstall.ps1") `
-Value "Write-Host `"Hello World! from `$env:COMPUTERNAME`";choco install Git" -Force
Invoke-BoxstarterBuild HelloWorld
$creds = Get-Credential win\mwrock
Install-BoxstarterPackage -ComputerName win `
-Package HelloWorld -Credential $creds
NOTE: PowerShell Remoting must be enabled on the remote machine. Launch a PowerShell Console as administrator:
Enable-PSRemoting -Force
Please see the Boxstarter docs.
Boxstarter requires the following to work:
Apache 2.0 - see LICENSE and NOTICE files.
If you are an open source user requesting support, please remember that most folks in the Chocolatey community are volunteers that have lives outside of open source and are not paid to ensure things work for you, so please be considerate of others' time when you are asking for things. Many of us have families that also need time as well and only have so much time to give on a daily basis. A little consideration and patience can go a long way. After all, you are using a pretty good tool without cost. It may not be perfect (yet), and we know that.
Observe the following help for submitting an issue.
-Debug -Verbose
(ie. Install-Boxstarter -PackageName <PACKAGE NAME OR GIST> -Verbose -Debug
. If it is less than 50 lines you can submit that with the issue or if it is longer, create a gist and link it.choco.exe
, then it logs to a file in $env:ChocolateyInstall\log\
. You can grab the specific log output from there so you don't have to capture or redirect screen output. Please limit the amount included to just the command run (the log is appended to with every command).log.sh
) and link to the gist from the issue. You can create it as secret so it doesn't fill up against your public gists but anyone with a direct link can still get to secret gists. If you accidentally include secret information in your gist, please delete it and create a new one (gist history can be seen by anyone) and update the link in the issue (issue history is not retained except by email - deleting the gist ensures that no one can get to it). Using gists this way also keeps accidental secrets from being shared in the issue in the first place as well.If you would like to contribute code or help squash a bug or two, that's awesome. Please familiarize yourself with CONTRIBUTING.
Committers, you should be very familiar with COMMITTERS.