gavin/windows-dev-box-setup-scripts
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Started a demoscripts folder, refactored some helper scripts (#70)

Browse Source 
* moving all recipes to dynamically find helper scripts
* started to a devops_azure script
* re-organizing some existing scripts
* updated Readme known issues
This commit is contained in:
Yosef Durr
2018-09-18 09:37:18 -07:00
committed by GitHub
parent 01c3847732
commit 79bbe5bdc4
11 changed files with 125 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -49,7 +49,8 @@ with a non-blank password. Use this user going forward. For more info on WSL ple
2. If you're a Node.js contributor working on Node.js core, please see the [Node.js Bootstrapping Guide](https://github.com/nodejs/node/tree/master/tools/bootstrap) or [click here to run](http://boxstarter.org/package/nr/url?https://raw.githubusercontent.com/nodejs/node/master/tools/bootstrap/windows_boxstarter).
## Known issues
- Reboot is not always logging you back in to resume the script. This is being tracked [here](https://github.com/chocolatey/boxstarter/issues/318). If you experience this please login manually and the script will continue running.
- The Boxstarter ClickOnce installer does not work when using Chrome. This issue is being tracked [here](https://github.com/chocolatey/boxstarter/issues/345). 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](https://github.com/chocolatey/boxstarter/issues/318). 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: https://github.com/chocolatey/boxstarter/issues/301
## Working with Chocolatey in an organization?