Skip to content

Instantly share code, notes, and snippets.

Rob Reynolds ferventcoder

Block or report user

Report or block ferventcoder

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@ferventcoder
ferventcoder / ChocolateyForTheOrganizations_EasilyManageSoftwareOnWindows.md
Last active May 1, 2019
Chocolatey for the Organizations: Easily Manage Software on Windows
View ChocolateyForTheOrganizations_EasilyManageSoftwareOnWindows.md

Do any of these apply to you?

  • "I've used Chocolatey at home and would like to see how I can use it at work."
  • "We are already using it in the office and want to validate we are 'doing it right'."
  • "I'm looking for a better way to manage Windows software."
  • "You had me at chocolate. Now I'm hungry."

Great! Chocolatey makes software management on Windows like slicing through butter with a hot knife. Easy! I'm saying it makes Windows software management easy. Okay, the analogy may not translate well, but that doesn't matter.

Come learn more about how to set up a full environment in a short amount of time and see some tools that will help you master Windows software management.

View ChocolateyLocalInstall.ps1
# use an internal repository to download Chocolatey nupkg to the local path:
$packageRepo = '<INSERT REPO URL>'
# uncomment if you want to download the file from a remote OData (HTTP/HTTPS) internal url (such as Artifactory, Nexus, ProGet, or Chocolatey.Server)
#$searchUrl = ($packageRepo.Trim('/'), 'Packages()?$filter=(Id%20eq%20%27chocolatey%27)%20and%20IsLatestVersion') -join '/'
# UPDATE THIS PATH
$localChocolateyPackageFilePath = "$env:SystemDrive\choco-setup\packages\chocolatey.0.10.0.nupkg"
# Determine unzipping method
# 7zip is the most compatible, but you need an internally hosted 7za.exe.
# Make sure the version matches for the arguments as well.
@ferventcoder
ferventcoder / disablechromeautoupdate.ps1
Created Feb 9, 2018
Disable Google Chrome Automatic Update Policy
View disablechromeautoupdate.ps1
$googlePoliciesKey = 'HKLM:\Software\Policies\Google'
if (!(Test-Path $googlePoliciesKey)) {
New-Item -Path $googlePoliciesKey -Force | Out-Null
}
New-ItemProperty $googlePoliciesKey -Name 'UpdateDefault' -Value 0 -PropertyType DWORD -Force | Out-Null
@ferventcoder
ferventcoder / _TODO.txt
Last active Aug 20, 2017
Chocolatey v0.10.8 Packaging
View _TODO.txt
TODO
1. Determine Package Use:
Organization? Internal Use? - You are not subject to distribution
rights when you keep everything internal. Put the binaries directly
into the tools directory (as long as total nupkg size is under 1GB).
When bigger, look to use from a share or download binaries from an
internal location. Embedded binaries makes for the most reliable use
of Chocolatey. Use `$fileLocation` (`$file`/`$file64`) and
View keybase.md

Keybase proof

I hereby claim:

  • I am ferventcoder on github.
  • I am ferventcoder (https://keybase.io/ferventcoder) on keybase.
  • I have a public key whose fingerprint is 93AC EB2C DA8C A198 6F9E 1A04 EDD4 A26E 428C 7DC8

To claim this, I am signing this object:

@ferventcoder
ferventcoder / PuppetConf2017_Abstract.md
Created Apr 22, 2017
Modern Software Management on Windows with Chocolatey and Puppet - PuppetConf2017 Abstract
View PuppetConf2017_Abstract.md

Modern Software Management on Windows with Chocolatey and Puppet

Traditional approaches to software management on Windows can be manual or inefficient. Chocolatey was designed as a common sense, flexible approach to managing software on Windows, both internal and 3rd party.

Chocolatey is a single, unified interface designed to easily work with all aspects of managing Windows software using a packaging framework that understands both versioning and dependency requirements. Chocolatey packages encapsulate everything required to manage a particular piece of software into one deployment artifact by wrapping installers, executables, zips, and scripts into a compiled package file.

Configuration management alone without a great package manager will only get you so far. Putting package management with configuration management (Puppet) makes an awesome story for Windows automation! Come learn more about Chocolatey and how we are taking Windows to the next level for automation.

@ferventcoder
ferventcoder / chocolateyInstall.ps1
Last active Apr 1, 2017
Unlock Functionality in Newer Versions with PolyFill for older
View chocolateyInstall.ps1
if ([System.Version]$env:CHOCOLATEY_VERSION -ge [System.Version]'0.10.4'){
# do something awesome
} else {
# implement additional functionality
}
View ContinuousDeploymentOnWindows.md

Let's face it - continuous deployment (continuous deployment) for many is a pipe dream. It's difficult, it's hard to support, and it's hard to get right. Finding the best tools for the job can be difficult. Ensuring there is a clear trace back to source can also be difficult. In this talk we will broach such subjects as:

  • Benefits and Requirements of CD (The why)
  • How CD works in every organization (remember, CD is not just about production deployments)
  • Fundamentals of Software development and why they are crucial to CD
  • The best tools available (although maybe a slight bias here, Rob will welcome other folks a quick 30 seconds to make cases for alternatives Rob doesn't mention)
  • Patterns of Deployment based on experience (The how)

Rob has over 10 years experience in infrastructure automation and has worked with continuous deployment approaches since 2006.

View PowerShellCommand.ps1
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$psFileFullPath = Join-Path $toolsDir "ps1crash.ps1"
Install-BinFile `
-Name ps1crash `
-Path "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe" `
-Command "-NoProfile -ExecutionPolicy unrestricted -Command `"&'$psFileFullPath' %*`""
@ferventcoder
ferventcoder / NonAdmin.cmd
Last active Oct 12, 2019
Installing Software as a Non-Administrator Using Chocolatey
View NonAdmin.cmd
:: Pick one of these two files (cmd or ps1)
:: Set directory for installation - Chocolatey does not lock
:: down the directory if not the default
SET INSTALLDIR=c:\ProgramData\chocoportable
setx ChocolateyInstall %INSTALLDIR%
:: All install options - offline, proxy, etc at
:: https://chocolatey.org/install
@powershell -NoProfile -ExecutionPolicy Bypass -Command "(iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))) >$null 2>&1" && SET PATH="%PATH%;%INSTALLDIR%\bin"
You can’t perform that action at this time.