Silpheel's dotfiles for Windows

A collection of PowerShell files for Windows, including common application installation through Chocolatey and npm, and developer-minded Windows configuration defaults.

Forked from Jay Harris' dotfiles for Windows

Installation

Using Git and the bootstrap script

You can clone the repository wherever you want. (I like to keep it in ~\Projects\dotfiles-windows.) The bootstrapper script will copy the files to your PowerShell Profile folder.

From PowerShell:

git clone https://github.com/silpheel/dotfiles-windows.git; cd dotfiles-windows; . .\bootstrap.ps1

To update your settings, cd into your local dotfiles-windows repository within PowerShell and then:

. .\bootstrap.ps1

Note: You must have your execution policy set to unrestricted (or at least in bypass) for this to work: Set-ExecutionPolicy Unrestricted.

Git-free install

Note: You must have your execution policy set to unrestricted (or at least in bypass) for this to work. To set this, run Set-ExecutionPolicy Unrestricted from a PowerShell running as Administrator.

To install these dotfiles from PowerShell without Git:

iex ((new-object net.webclient).DownloadString('https://raw.github.com/silpheel/dotfiles-windows/master/setup/install.ps1'))

To update later on, just run that command again.

Add custom commands without creating a new fork

If .\extra.ps1 exists, it will be sourced along with the other files. You can use this to add a few custom commands without the need to fork this entire repository, or to add commands you don't want to commit to a public repository.

Sensible Windows defaults

When setting up a new Windows PC, you may want to set some Windows defaults and features, such as showing hidden files in Windows Explorer and installing IIS. This will also set your machine name and full user name, so you may want to modify this file before executing.

.\windows.ps1

Install dependencies and packages

When setting up a new Windows box, you may want to install some common packages, utilities, and dependencies. These could include node.js packages via NPM, Chocolatey packages, Windows Features and Tools via Web Platform Installer, and Visual Studio Extensions from the Visual Studio Gallery.

.\deps.ps1

The scripts will install Chocolatey, node.js, and WebPI if necessary.

Visual Studio Extensions
Extensions will be installed into your most current version of Visual Studio. You can also install additional plugins at any time via Install-VSExtension $url. The Url can be found on the gallery; it's the extension's Download link url.

Forking your own version

If you do fork for your own custom configuration, you will need to touch a few files to reference your own repository, instead of mine.

Within /setup/install.ps1, modify the Repository variables.

$account = "YourUsernameHere"
$repo    = "dotfiles-windows"
$branch  = "master"

Within the Windows Defaults file, /windows.ps1, modify the Machine name on the first line.

Rename-Computer -NewName "MyMachineName" | Out-Null

Finally, be sure to reference your own repository in the git-free installation command.

iex ((new-object net.webclient).DownloadString('https://raw.github.com/$account/$repo/$branch/setup/install.ps1'))

Feedback

Suggestions/improvements are welcome and encouraged!

Author

Jay Harris

Thanks to…

• @Mathias Bynens for his OS X dotfiles, which this repository is modeled after.