ferventcoder

Function Convert-FitbitToWithingsWeightMeasurements {
  [CmdletBinding()]
  Param(
    [Parameter()]
    [String]
    $Folder =(Get-Location).Path
  )

  # Create a collection (a List for memory efficiency) to hold output
  $WithingsWeightMeasurements = New-Object System.Collections.Generic.List[System.Object]

ferventcoder

Chocolatey Software, Inc - Contributor License Agreement V1.0

Thank you for your interest in contributing to Chocolatey Software, Inc ("Chocolatey Software").

This Contributor License Agreement ("Agreement" or "CLA") documents the rights granted by Contributors to Chocolatey Software. The Agreement may cover more than one software project managed by Chocolatey Software. In order to clarify the intellectual property license granted with Contributions from any person or entity, Chocolatey Software must have a CLA agreed to by each Contributor. This Agreement is for your protection as a Contributor as well as the protection of Chocolatey Software; it does not change your rights to use your own Contributions for any other purpose.

Either individuals or business entities, including without limitation, all employees or agents acting on behalf of such entity (an "Entity"), may submit Contributions to Chocolatey Software under this Agreement.

Please read this document carefully before agreeing

ferventcoder

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.

ferventcoder

# 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

$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

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 

ferventcoder

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

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

if ([System.Version]$env:CHOCOLATEY_VERSION -ge [System.Version]'0.10.4'){
  # do something awesome
} else {
  # implement additional functionality
}

ferventcoder

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.