Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
-
STEP1
Package Review
-
STEP2
Integration Method
-
STEP3
Internal Repo Url
-
STEP4
Environment Setup
-
STEP5
Install Script
Step 1: Review Your Packages
Step 2: Choose Your Integration Method
Step 3: Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
Step 3: Copy Your Script or Download Config
Option 1: Copy Script
Option 2: Download Config
Step 4: Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
-
You can also just download the packages and push them to a repository
Download Packages
-
Open Source
-
Download the packages:
Download Packages - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
-
For package and dependencies run:
- Automate package internalization
-
Run: (additional options)
Step 5: Copy Your Script
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"
#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
#### We use this variable for future REST calls.
$RequestArguments = @{
UseBasicParsing = $true
}
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.1.1.0.nupkg"
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
$TempDirectory = Join-Path $env:Temp "chocolateyInstall"
if (-not (Test-Path $TempDirectory -PathType Container)) {
$null = New-Item -Path $TempDirectory -ItemType Directory
}
$DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments
#### Extract the Nupkg, and run the chocolateyInstall script
if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
} else {
# PowerShell versions <4.0 do not have this function available
try {
$shellApplication = New-Object -ComObject Shell.Application
$zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
$destinationFolder = $shellApplication.NameSpace($TempDirectory)
$destinationFolder.CopyHere($zipPackage.Items(), 0x10)
} catch {
Write-Warning "Unable to unzip package using built-in compression."
throw $_
}
}
& $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
refreshenv
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400
#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress
### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
choco source remove -n $_.Name
}
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco source disable --name chocolatey.licensed
} else {
Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
if ($ChocolateyCentralManagementClientSalt) {
choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
}
if ($ChocolateyCentralManagementServiceSalt) {
choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
}
choco feature enable --name useChocolateyCentralManagement
choco feature enable --name useChocolateyCentralManagementDeployments
}
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy
- name: Install and Configure Chocolatey
hosts: all
## 2. TOP LEVEL VARIABLES ##
vars:
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
nuget_repository_url: INTERNAL REPO URL
### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
# nuget_repository_username: username
# nuget_repository_password: password
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService
#### ii. If using a Client Salt, add it here
# chocolatey_central_management_client_salt: clientsalt
#### iii. If using a Service Salt, add it here
# chocolatey_central_management_service_salt: servicesalt
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
tasks:
- name: Install chocolatey
win_chocolatey:
name: chocolatey
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# - name: Enable FIPS compliance
# win_chocolatey_feature:
# name: useFipsCompliantChecksums
# state: enabled
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
- name: Set the cache location
win_chocolatey_config:
name: cacheLocation
state: present
value: C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
- name: Set the command execution timeout
win_chocolatey_config:
name: commandExecutionTimeoutSeconds
state: present
value: 14400
#### Turn off download progress when running choco through integrations
- name: Disable showing download progress
win_chocolatey_feature:
name: showDownloadProgress
state: disabled
### c. Sources ###
#### Remove the default community package repository source
- name: Remove Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey
state: absent
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
- name: Add Internal Repository
win_chocolatey_source:
name: ChocolateyInternal
state: present
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
priority: 1
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
- name: Upgrade Chocolatey
win_chocolatey:
name: chocolatey
state: latest
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
- name: Install Chocolatey License
win_chocolatey:
name: chocolatey-license
source: ChocolateyInternal
state: latest
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
- name: Disable Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey.licensed
state: disabled
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
- name: Install Chocolatey Extension
win_chocolatey:
name: chocolatey.extension
source: ChocolateyInternal
state: latest
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
- name: Hide not-elevated warnings
win_chocolatey_feature:
name: showNonElevatedWarnings
state: disabled
- name: Use background mode for self-service
win_chocolatey_feature:
name: useBackgroundService
state: enabled
- name: Use background service for non-admins
win_chocolatey_feature:
name: useBackgroundServiceWithNonAdministratorsOnly
state: enabled
- name: Allow background uninstallation for user installs
win_chocolatey_feature:
name: allowBackgroundServiceUninstallsFromUserInstallsOnly
state: enabled
- name: Set allowed background service commands
win_chocolatey_config:
name: backgroundServiceAllowedCommands
state: present
value: install,upgrade,uninstall
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
- name: Install Chocolatey Agent
when: chocolatey_central_management_url is defined
win_chocolatey:
name: chocolatey-agent
source: ChocolateyInternal
state: latest
- name: Set the Central Management Service URL
when: chocolatey_central_management_url is defined
win_chocolatey_config:
name: CentralManagementServiceUrl
state: present
value: {{ chocolatey_central_management_url }}
- name: Set the Central Management Client Salt
when: chocolatey_central_management_client_salt is defined
win_chocolatey_config:
name: centralManagementClientCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_client_salt }}
- name: Set the Central Management Service Salt
when: chocolatey_central_management_service_salt is defined
win_chocolatey_config:
name: centralManagementServiceCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_service_salt }}
- name: Use Central Management
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagement
state: enabled
- name: Use Central Management Deployments
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagementDeployments
state: enabled
See docs at https://docs.chef.io/resource_chocolatey_package.html.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg",
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
# action :enable
# end
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
value 'C:\ProgramData\chocolatey\cache'
end
#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
value '14400'
end
#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
action :disable
end
### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
action :remove
end
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
source "#{NugetRepositoryUrl}"
priority 1
action :add
end
execute 'ChocolateyInternal' do
command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
action :upgrade
source "#{NugetRepositoryUrl}"
end
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
action :install
source "#{NugetRepositoryUrl}"
end
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
action :disable
end
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
action install
source "#{NugetRepositoryUrl}"
end
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
action :disable
end
chocolatey_feature 'useBackgroundService' do
action :enable
end
chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
action :enable
end
chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
action :enable
end
chocolatey_config 'backgroundServiceAllowedCommands' do
value 'install,upgrade,uninstall'
end
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
action install
source "#{NugetRepositoryUrl}"
# user "#{NugetRepositoryUsername}"
# password "#{NugetRepositoryPassword}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'CentralManagementServiceUrl' do
value "#{ChocolateyCentralManagementUrl}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementClientSalt}"
only_if { ChocolateyCentralManagementClientSalt != nil }
end
chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementServiceSalt}"
only_if { ChocolateyCentralManagementServiceSalt != nil }
end
chocolatey_feature 'useChocolateyCentralManagement' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_feature 'useChocolateyCentralManagementDeployments' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
If Applicable - Chocolatey Configuration/Installation
#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
$null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
}
Install-Module -Name cChoco
if ($PSGallery.InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
}
}
#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1
Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
param(
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL",
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg",
### c. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# ),
### d. Install.ps1 URL
#### The path to the hosted install script:
$ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"
### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt",
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
)
Import-DscResource -ModuleName PSDesiredStateConfiguration
Import-DscResource -ModuleName cChoco
Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
Environment chocoDownloadUrl {
Name = "chocolateyDownloadUrl"
Value = $ChocolateyNupkgUrl
}
cChocoInstaller installChocolatey {
DependsOn = "[Environment]chocoDownloadUrl"
InstallDir = Join-Path $env:ProgramData "chocolatey"
ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# cChocoFeature featureFipsCompliance {
# FeatureName = "useFipsCompliantChecksums"
# }
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
cChocoConfig cacheLocation {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "cacheLocation"
Value = "C:\ProgramData\chocolatey\cache"
}
#### Increase timeout to at least 4 hours
cChocoConfig commandExecutionTimeoutSeconds {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "commandExecutionTimeoutSeconds"
Value = 14400
}
#### Turn off download progress when running choco through integrations
cChocoFeature showDownloadProgress {
DependsOn = "[cChocoInstaller]installChocolatey"
FeatureName = "showDownloadProgress"
Ensure = "Absent"
}
### c. Sources ###
#### Remove the default community package repository source
cChocoSource removeCommunityRepository {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "chocolatey"
Ensure = "Absent"
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
cChocoSource addInternalSource {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "ChocolateyInternal"
Source = $NugetRepositoryUrl
Credentials = $NugetRepositoryCredential
Priority = 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
cChocoPackageInstaller updateChocolatey {
DependsOn = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
Name = "chocolatey"
AutoUpgrade = $true
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
cChocoPackageInstaller chocolateyLicense {
DependsOn = "[cChocoPackageInstaller]updateChocolatey"
Name = "chocolatey-license"
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
Script disableLicensedSource {
DependsOn = "[cChocoPackageInstaller]chocolateyLicense"
GetScript = {
$Source = choco source list --limitoutput | `
ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
Where-Object Name -eq "chocolatey.licensed"
return @{
Result = if ($Source) {
[bool]::Parse($Source.Disabled)
} else {
Write-Warning "Source 'chocolatey.licensed' was not present."
$true # Source does not need disabling
}
}
}
SetScript = {
$null = choco source disable --name "chocolatey.licensed"
}
TestScript = {
$State = [ScriptBlock]::Create($GetScript).Invoke()
return $State.Result
}
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
cChocoPackageInstaller chocolateyLicensedExtension {
DependsOn = "[Script]disableLicensedSource"
Name = "chocolatey.extension"
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
cChocoFeature hideElevatedWarnings {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "showNonElevatedWarnings"
Ensure = "Absent"
}
cChocoFeature useBackgroundService {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundService"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceWithNonAdmins {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
Ensure = "Present"
}
cChocoConfig allowedBackgroundServiceCommands {
DependsOn = "[cChocoFeature]useBackgroundService"
ConfigName = "backgroundServiceAllowedCommands"
Value = "install,upgrade,uninstall"
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
cChocoPackageInstaller chocolateyAgent {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
Name = "chocolatey-agent"
}
cChocoConfig centralManagementServiceUrl {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "CentralManagementServiceUrl"
Value = $ChocolateyCentralManagementUrl
}
if ($ChocolateyCentralManagementClientSalt) {
cChocoConfig centralManagementClientSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementClientSalt
}
}
if ($ChocolateyCentralManagementServiceSalt) {
cChocoConfig centralManagementServiceSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementServiceSalt
}
}
cChocoFeature useCentralManagement {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagement"
Ensure = "Present"
}
cChocoFeature useCentralManagementDeployments {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagementDeployments"
Ensure = "Present"
}
}
}
}
# If working this into an existing configuration with a good method for
$ConfigData = @{
AllNodes = @(
@{
NodeName = "localhost"
PSDscAllowPlainTextPassword = $true
}
)
}
try {
Push-Location $env:Temp
$Config = ChocolateyConfig -ConfigurationData $ConfigData
Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
Pop-Location
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
#### See https://forge.puppet.com/puppetlabs/chocolatey
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg'
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'
#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
### source locations. This is directly to the bare download url for the
### chocolatey.nupkg, similar to what you see when you browse to
### https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
chocolatey_download_url => $_choco_download_url,
use_7zip => false,
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#chocolateyfeature {'useFipsCompliantChecksums':
# ensure => enabled,
#}
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
value => 'C:\ProgramData\chocolatey\cache',
}
#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
value => '14400',
}
#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
ensure => disabled,
}
### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
ensure => absent,
location => 'https://community.chocolatey.org/api/v2/',
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
ensure => present,
location => $_repository_url,
priority => 1,
username => 'optional',
password => 'optional,not ensured',
bypass_proxy => true,
admin_only => false,
allow_self_service => false,
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
package {'chocolatey':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license
# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
ensure => disabled,
priority => '10',
user => 'customer',
password => '1234',
require => Package['chocolatey-license'],
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
ensure => disabled,
}
chocolateyfeature {'useBackgroundService':
ensure => enabled,
}
chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
ensure => enabled,
}
chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
ensure => enabled,
}
chocolateyconfig {'backgroundServiceAllowedCommands':
value => 'install,upgrade,uninstall',
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
package {'chocolatey-agent':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
chocolateyconfig {'CentralManagementServiceUrl':
value => $_chocolatey_central_management_url,
}
if $_chocolatey_central_management_client_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
if $_chocolatey_central_management_service_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
chocolateyfeature {'useChocolateyCentralManagement':
ensure => enabled,
require => Package['chocolatey-agent'],
}
chocolateyfeature {'useChocolateyCentralManagementDeployments':
ensure => enabled,
require => Package['chocolatey-agent'],
}
}
Need Help? View our docs or file an issue.
There is already a version of this package in your Script Builder
Current Version | New Version |
---|---|
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
107,340
Downloads of v 2.0.8:
297
Last Update:
02 Aug 2021
Package Maintainer(s):
Software Author(s):
- Rick Strahl
- West Wind Technologies
Tags:
markdown markdown-editor markdown-generator markdown-blogging documentation writing weblog blogging westwind admin
Markdown Monster
This is not the latest version of Markdown Monster available.
- 1
- 2
- 3
2.0.8 | Updated: 02 Aug 2021
Downloads:
107,340
Downloads of v 2.0.8:
297
Maintainer(s):
Software Author(s):
- Rick Strahl
- West Wind Technologies
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
- 1
- 2
- 3
Markdown Monster
2.0.8
This is not the latest version of Markdown Monster available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Markdown Monster, run the following command from the command line or from PowerShell:
To upgrade Markdown Monster, run the following command from the command line or from PowerShell:
To uninstall Markdown Monster, run the following command from the command line or from PowerShell:
Deployment Method:
📝 NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download markdownmonster --internalize --version=2.0.8 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade markdownmonster -y --source="'INTERNAL REPO URL'" --version="'2.0.8'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade markdownmonster -y --source="'INTERNAL REPO URL'" --version="'2.0.8'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install markdownmonster
win_chocolatey:
name: markdownmonster
version: '2.0.8'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'markdownmonster' do
action :install
source 'INTERNAL REPO URL'
version '2.0.8'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller markdownmonster
{
Name = "markdownmonster"
Version = "2.0.8"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'markdownmonster':
ensure => '2.0.8',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
There are versions of this package awaiting moderation . See the Version History section below.
This package was approved as a trusted package on 02 Aug 2021.
Markdown Monster is an easy to use and extensible Markdown Editor, Viewer and Weblog Publisher. The editor sports syntax colored editing of Markdown text, inline spell checking, live, synced HTML preview, a document outline, integrated file browser and Git support. You can embed images by pasting from clipboard, embedding via dialog or dragging images from the shell. Embed urls, code snippets and emojiis quickly and use the built-in table editor to create nicely formatted Markdown tables. There is support for text snippet expansion and C# script execution to automate and extend Markdown Monster.
But above all the editor's goal is to get out of your way and let you focus on your content creation, and to provide you with the right tools to get your job done efficiently.
Documents can be saved to HTML or PDF, you can generate HTML from partial selections and you can even convert exsternal HTML to Markdown. Markdown Monster can also publish your Markdown directly to your Weblog that supports WordPress, MetaWebLog or Medium APIs. You can manage multiple blogs and even download existing HTML posts as Markdown.
Markdown Monster can be extended using a .NET based add-in model and a few useful addins are available to provide features like storing images in Azure Blobs, Gist integration, a reusable Snippets manager, and more. You can also swap Markdown Parsers between Markdig and Pandoc and use another custom Markdown parser via addin integration. A command line interface lets you easily launch Markdown Monster with multiple files, or with a folder selected, and the included CLI can automate several Markdown conversions.
Markdown Monster can be evaluated for free. This package is unlimited and fully functional, but a license is required for continued use. Although Markdown Monster is licensed software, the source code is available in the open on GitHub. Requires .NET 4.7.2 or later.
A portable, non-admin Chocolatey install is also available in MarkdownMonster.Portable.
$packageName = 'markdownmonster'
$fileType = 'exe'
$url = 'https://github.com/RickStrahl/MarkdownMonsterReleases/raw/master/v2/v2.0/MarkdownMonsterSetup-2.0.8.exe'
$silentArgs = '/VERYSILENT'
$validExitCodes = @(0)
Install-ChocolateyPackage "$packageName" "$fileType" "$silentArgs" "$url" -validExitCodes $validExitCodes -checksum "63B438B061BDECFC889BC1342381EC12A6EFF3A40FCE3474AB7158496FF38D17" -checksumType "sha256"
Markdown Monster License
-------------------------
Markdown Monster comes in several license modes: Evaluation, Single User, Multiple User and Site License.
Markdown Monster is **Source Open** with source code available on GitHub, but it is a licensed product that requires a paid-for license for continued use. The software is licensed as (c) Rick Strahl, West Wind Technologies, 2015-2020.
A fully functional, free evaluation version is available for evaluation use, but continued use requires purchase of a license.
Licenses can be purchased from:
http://store.west-wind.com/product/markdown_monster
EVALUATION LICENSE
The Evaluation version has all the features and functionality of the registered version, except that it shows occasional freeware notices. Tampering with or removing of the notices is not allowed with the evaluation license.
You can use the evaluation version with the notices enabled, but if you use Markdown Monster regularly or for commercial use, please register and support further development and maintenance.
PURCHASED LICENSE
For continued or commercial use of Markdown Monster a paid-for license is required. The paid-for license removes the freeware notices.
Each licensed user must have a separate license, but a single user may use multiple copies of Markdown Monster on multiple machines.
The multi-user licenses work the same as a single user license applied to the number of users specified on the license purchased. An organizational site license is available to allow any number of users running unlimited numbers of Markdown Monster instances within a single organization.
Any purchased license is valid for the duration of the major release that it was purchased for (ie. 1.00-1.99) and minor version updates within that major version are always free. Upgrade pricing is available for major version upgrades, usually at half of full price, and it's our policy to allow for free upgrades to the next major version within a year of purchase.
SOURCE CODE
Markdown Monster is **Source Open** and source code is available on GitHub at https://github.com/RickStrahl/MarkdownMonster, but the licensing outlined above is applies regardless. We allow modification of source code for internal use of Markdown Monster in your organization or for submitting pull requests to the Markdown Monster main repository. Under no circumstances are you allowed to re-package and re-distribute any part of Markdown Monster outside of your organization.
GET INVOLVED - GET A FREE LICENSE
We encourage pull requests for feature suggestions or bug fixes to be submitted back to the Markdown Monster repository. Any contributors that provide meaningful enhancements, help with identifying and or fixing of bugs or by actively promoting Markdown Monster can qualify for a free license (at our discretion). Additionally Microsoft MVPs and Insiders and Microsoft Employees can apply for a free license.
WARRANTY DISCLAIMER: NO WARRANTY!
YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT USE OF THE LICENSED APPLICATION IS AT YOUR SOLE RISK AND THAT THE ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFORMANCE, ACCURACY AND EFFORT IS WITH YOU. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSE APPLICATION AND ANY SERVICES PERFORMED OR PROVIDED BY THE LICENSED APPLICATION ("SERVICES") ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND, AND APPLICATION PROVIDER HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH RESPECT TO THE LICENSED APPLICATION AND ANY SERVICES, EITHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES AND/OR CONDITIONS OF MERCHANTABILITY, OF SATISFACTORY QUALITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF ACCURACY, OF QUIET ENJOYMENT, AND NON-INFRINGEMENT OF THIRD PARTY RIGHTS. APPLICATION PROVIDER DOES NOT WARRANT AGAINST INTERFERENCE WITH YOUR ENJOYMENT OF THE LICENSED APPLICATION, THAT THE FUNCTIONS CONTAINED IN, OR SERVICES PERFORMED OR PROVIDED BY, THE LICENSED APPLICATION WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE LICENSED APPLICATION OR SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT EFFECTS IN THE LICENSED APPLICATION OR SERVICES WILL BE CORRECTED. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY APPLICATION PROVIDER OR ITS AUTHORIZED REPRESENTATIVE SHALL CREATE A WARRANTY. SHOULD THE LICENSED APPLICATION OR SERVICES PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
IN NO EVENT SHALL THE AUTHOR, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THIS PROGRAM AND DOCUMENTATION, BE LIABLE FOR ANY COMMERCIAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM INCLUDING, BUT NOT LIMITED TO, LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS, EVEN IF YOU OR OTHER PARTIES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Log in or click on link to see number of positives.
- MarkdownMonster.2.0.8.nupkg (7febf77ef06b) - ## / 61
- MarkdownMonsterSetup-2.0.8.exe (63b438b061bd) - ## / 69
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Markdown Monster 2.5.4 | 4 | Tuesday, May 17, 2022 | Pending Automated Review | |
Markdown Monster 2.5.3 | 175 | Friday, May 13, 2022 | Approved | |
Markdown Monster 2.5 | 177 | Tuesday, May 10, 2022 | Approved | |
Markdown Monster 2.4.13 | 290 | Friday, April 29, 2022 | Approved | |
Markdown Monster 2.4.12 | 141 | Wednesday, April 27, 2022 | Approved | |
Markdown Monster 2.4.10 | 265 | Sunday, April 17, 2022 | Approved | |
Markdown Monster 2.4.9 | 242 | Tuesday, April 12, 2022 | Approved | |
Markdown Monster 2.4.8 | 152 | Saturday, April 9, 2022 | Approved | |
Markdown Monster 2.4.7 | 246 | Friday, April 1, 2022 | Approved | |
Markdown Monster 2.4.6 | 358 | Saturday, March 19, 2022 | Approved | |
Markdown Monster 2.4.5 | 160 | Wednesday, March 16, 2022 | Approved | |
Markdown Monster 2.4.3 | 94 | Wednesday, March 16, 2022 | Approved | |
Markdown Monster 2.4 | 234 | Thursday, March 10, 2022 | Approved | |
Markdown Monster 2.3.19 | 93 | Wednesday, March 9, 2022 | Approved | |
Markdown Monster 2.3.18 | 94 | Monday, March 7, 2022 | Approved | |
Markdown Monster 2.3.17 | 372 | Saturday, February 19, 2022 | Approved | |
Markdown Monster 2.3.15 | 197 | Wednesday, February 16, 2022 | Approved | |
Markdown Monster 2.3.14 | 181 | Sunday, February 13, 2022 | Approved | |
Markdown Monster 2.3.12 | 189 | Wednesday, February 9, 2022 | Approved | |
Markdown Monster 2.3.10 | 225 | Friday, February 4, 2022 | Approved | |
Markdown Monster 2.3.8 | 106 | Thursday, February 3, 2022 | Approved | |
Markdown Monster 2.3.7 | 224 | Saturday, January 29, 2022 | Approved | |
Markdown Monster 2.3.6 | 221 | Tuesday, January 25, 2022 | Approved | |
Markdown Monster 2.3.4 | 192 | Friday, January 21, 2022 | Approved | |
Markdown Monster 2.3.1 | 240 | Sunday, January 16, 2022 | Approved | |
Markdown Monster 2.3 | 163 | Thursday, January 13, 2022 | Approved | |
Markdown Monster 2.2.8 | 163 | Monday, January 10, 2022 | Approved | |
Markdown Monster 2.2.5 | 255 | Tuesday, January 4, 2022 | Approved | |
Markdown Monster 2.2.4 | 212 | Wednesday, December 29, 2021 | Approved | |
Markdown Monster 2.2.3 | 266 | Monday, December 20, 2021 | Approved | |
Markdown Monster 2.2.2 | 384 | Tuesday, December 7, 2021 | Approved | |
Markdown Monster 2.2 | 395 | Tuesday, November 23, 2021 | Approved | |
Markdown Monster 2.1.8 | 210 | Thursday, November 18, 2021 | Approved | |
Markdown Monster 2.1.7 | 306 | Thursday, November 11, 2021 | Approved | |
Markdown Monster 2.1.6 | 238 | Monday, November 8, 2021 | Approved | |
Markdown Monster 2.1.5.1 | 194 | Thursday, November 4, 2021 | Approved | |
Markdown Monster 2.1.5 | 119 | Tuesday, November 2, 2021 | Approved | |
Markdown Monster 2.1.4 | 281 | Wednesday, October 27, 2021 | Approved | |
Markdown Monster 2.1.3 | 228 | Friday, October 22, 2021 | Approved | |
Markdown Monster 2.1.2 | 218 | Tuesday, October 19, 2021 | Approved | |
Markdown Monster 2.1 | 302 | Wednesday, October 13, 2021 | Approved | |
Markdown Monster 2.0.19 | 244 | Saturday, October 9, 2021 | Approved | |
Markdown Monster 2.0.18 | 255 | Monday, October 4, 2021 | Approved | |
Markdown Monster 2.0.17 | 257 | Wednesday, September 29, 2021 | Approved | |
Markdown Monster 2.0.16 | 109 | Monday, September 27, 2021 | Approved | |
Markdown Monster 2.0.15 | 313 | Sunday, September 19, 2021 | Approved | |
Markdown Monster 2.0.14 | 126 | Friday, September 17, 2021 | Approved | |
Markdown Monster 2.0.13 | 304 | Friday, September 10, 2021 | Approved | |
Markdown Monster 2.0.12 | 302 | Wednesday, September 1, 2021 | Approved | |
Markdown Monster 2.0.11 | 402 | Thursday, August 19, 2021 | Approved | |
Markdown Monster 2.0.9 | 320 | Tuesday, August 10, 2021 | Approved | |
Markdown Monster 2.0.8 | 297 | Monday, August 2, 2021 | Approved | |
Markdown Monster 2.0.7 | 204 | Thursday, July 29, 2021 | Approved | |
Markdown Monster 2.0.5 | 218 | Monday, July 26, 2021 | Approved | |
Markdown Monster 2.0.3 | 239 | Wednesday, July 21, 2021 | Approved | |
Markdown Monster 1.28.5 | 127 | Monday, July 19, 2021 | Approved | |
Markdown Monster 1.28.4 | 405 | Wednesday, July 7, 2021 | Approved | |
Markdown Monster 1.28.3 | 361 | Saturday, June 26, 2021 | Approved | |
Markdown Monster 1.28.2 | 77 | Saturday, June 26, 2021 | Approved | |
Markdown Monster 1.28 | 501 | Tuesday, June 8, 2021 | Approved | |
Markdown Monster 1.27.9 | 212 | Saturday, June 5, 2021 | Approved | |
Markdown Monster 1.27.8 | 393 | Monday, May 24, 2021 | Approved | |
Markdown Monster 1.27.7.1 | 261 | Thursday, May 20, 2021 | Approved | |
Markdown Monster 1.27.7 | 47 | Wednesday, May 19, 2021 | Approved | |
Markdown Monster 1.27.6 | 241 | Sunday, May 16, 2021 | Approved | |
Markdown Monster 1.27.5 | 151 | Friday, May 14, 2021 | Approved | |
Markdown Monster 1.27.4 | 193 | Tuesday, May 11, 2021 | Approved | |
Markdown Monster 1.27.2 | 336 | Tuesday, May 4, 2021 | Approved | |
Markdown Monster 1.27.1 | 230 | Friday, April 30, 2021 | Approved | |
Markdown Monster 1.26.14 | 240 | Monday, April 26, 2021 | Approved | |
Markdown Monster 1.26.12 | 416 | Thursday, April 15, 2021 | Approved | |
Markdown Monster 1.26.10 | 294 | Friday, April 9, 2021 | Approved | |
Markdown Monster 1.26.6 | 321 | Wednesday, March 31, 2021 | Approved | |
Markdown Monster 1.26.5 | 515 | Tuesday, March 16, 2021 | Approved | |
Markdown Monster 1.26.4 | 497 | Thursday, February 25, 2021 | Approved | |
Markdown Monster 1.26.3 | 351 | Wednesday, February 17, 2021 | Approved | |
Markdown Monster 1.26.2 | 295 | Saturday, February 13, 2021 | Approved | |
Markdown Monster 1.26 | 403 | Thursday, February 4, 2021 | Approved | |
Markdown Monster 1.25.16.3 | 374 | Friday, January 29, 2021 | Approved | |
Markdown Monster 1.25.16 | 564 | Tuesday, January 12, 2021 | Approved | |
Markdown Monster 1.25.15 | 351 | Wednesday, January 6, 2021 | Approved | |
Markdown Monster 1.25.14 | 434 | Tuesday, December 29, 2020 | Approved | |
Markdown Monster 1.25.13 | 345 | Thursday, December 24, 2020 | Approved | |
Markdown Monster 1.25.12 | 373 | Friday, December 11, 2020 | Approved | |
Markdown Monster 1.25.8 | 329 | Wednesday, December 2, 2020 | Approved | |
Markdown Monster 1.25.6 | 296 | Wednesday, November 25, 2020 | Approved | |
Markdown Monster 1.25.5 | 252 | Thursday, November 19, 2020 | Approved | |
Markdown Monster 1.25 | 336 | Wednesday, November 11, 2020 | Approved | |
Markdown Monster 1.24.14 | 424 | Thursday, October 29, 2020 | Approved | |
Markdown Monster 1.24.12.18 | 53 | Thursday, October 29, 2020 | Approved | |
Markdown Monster 1.24.12 | 513 | Monday, October 12, 2020 | Approved | |
Markdown Monster 1.24.9 | 374 | Wednesday, September 30, 2020 | Approved | |
Markdown Monster 1.24.8 | 272 | Thursday, September 24, 2020 | Approved | |
Markdown Monster 1.24 | 529 | Thursday, September 3, 2020 | Approved | |
Markdown Monster 1.23.18.3 | 306 | Thursday, August 27, 2020 | Approved | |
Markdown Monster 1.23.18 | 215 | Wednesday, August 26, 2020 | Approved | |
Markdown Monster 1.23.17.2 | 280 | Thursday, August 20, 2020 | Approved | |
Markdown Monster 1.23.17 | 163 | Wednesday, August 19, 2020 | Approved | |
Markdown Monster 1.23.15.2 | 349 | Sunday, August 9, 2020 | Approved | |
Markdown Monster 1.23.15 | 183 | Thursday, August 6, 2020 | Approved | |
Markdown Monster 1.23.14 | 552 | Thursday, July 16, 2020 | Approved | |
Markdown Monster 1.23.12 | 425 | Monday, July 6, 2020 | Approved | |
Markdown Monster 1.23 | 455 | Tuesday, June 23, 2020 | Approved | |
Markdown Monster 1.22.8 | 378 | Tuesday, June 9, 2020 | Approved | |
Markdown Monster 1.22.6 | 392 | Thursday, May 28, 2020 | Approved | |
Markdown Monster 1.22.4 | 516 | Tuesday, May 12, 2020 | Approved | |
Markdown Monster 1.22.3 | 283 | Friday, May 8, 2020 | Approved | |
Markdown Monster 1.22.2 | 398 | Thursday, April 30, 2020 | Approved | |
Markdown Monster 1.22 | 352 | Wednesday, April 22, 2020 | Approved | |
Markdown Monster 1.21.12 | 426 | Friday, April 10, 2020 | Approved | |
Markdown Monster 1.21.11 | 499 | Tuesday, March 24, 2020 | Approved | |
Markdown Monster 1.21.4 | 496 | Thursday, March 5, 2020 | Approved | |
Markdown Monster 1.21.2.1 | 446 | Wednesday, February 19, 2020 | Approved | |
Markdown Monster 1.21.2 | 132 | Wednesday, February 19, 2020 | Approved | |
Markdown Monster 1.21 | 607 | Monday, January 27, 2020 | Approved | |
Markdown Monster 1.20.12 | 404 | Friday, January 17, 2020 | Approved | |
Markdown Monster 1.20.10 | 424 | Monday, January 6, 2020 | Approved | |
Markdown Monster 1.20.8 | 294 | Thursday, January 2, 2020 | Approved | |
Markdown Monster 1.20.7 | 236 | Sunday, December 29, 2019 | Approved | |
Markdown Monster 1.20.5 | 432 | Friday, December 13, 2019 | Approved | |
Markdown Monster 1.20 | 638 | Friday, November 8, 2019 | Approved | |
Markdown Monster 1.19.15 | 338 | Monday, November 4, 2019 | Approved | |
Markdown Monster 1.19.14 | 161 | Sunday, November 3, 2019 | Approved | |
Markdown Monster 1.19.12.5 | 278 | Wednesday, October 30, 2019 | Approved | |
Markdown Monster 1.19.12 | 384 | Tuesday, October 22, 2019 | Approved | |
Markdown Monster 1.19.11 | 247 | Friday, October 18, 2019 | Approved | |
Markdown Monster 1.19.10 | 276 | Tuesday, October 15, 2019 | Approved | |
Markdown Monster 1.19.9 | 352 | Monday, October 7, 2019 | Approved | |
Markdown Monster 1.19.8 | 360 | Tuesday, October 1, 2019 | Approved | |
Markdown Monster 1.19.6 | 418 | Friday, September 20, 2019 | Approved | |
Markdown Monster 1.19.5 | 353 | Monday, September 16, 2019 | Approved | |
Markdown Monster 1.19.4 | 346 | Monday, September 9, 2019 | Approved | |
Markdown Monster 1.19 | 371 | Wednesday, September 4, 2019 | Approved | |
Markdown Monster 1.18.15 | 233 | Tuesday, September 3, 2019 | Approved | |
Markdown Monster 1.18.14 | 416 | Tuesday, August 27, 2019 | Approved | |
Markdown Monster 1.18.12 | 400 | Monday, August 19, 2019 | Approved | |
Markdown Monster 1.18.10 | 620 | Monday, July 22, 2019 | Approved | |
Markdown Monster 1.18.8 | 493 | Tuesday, July 9, 2019 | Approved | |
Markdown Monster 1.18.6 | 357 | Monday, July 1, 2019 | Approved | |
Markdown Monster 1.18.5 | 360 | Tuesday, June 25, 2019 | Approved | |
Markdown Monster 1.18.4 | 258 | Monday, June 24, 2019 | Approved | |
Markdown Monster 1.18 | 397 | Monday, June 17, 2019 | Approved | |
Markdown Monster 1.17.8 | 377 | Monday, June 10, 2019 | Approved | |
Markdown Monster 1.17.5 | 336 | Tuesday, June 4, 2019 | Approved | |
Markdown Monster 1.17.3 | 437 | Sunday, May 26, 2019 | Approved | |
Markdown Monster 1.17 | 474 | Tuesday, May 14, 2019 | Approved | |
Markdown Monster 1.16.18 | 295 | Friday, May 10, 2019 | Approved | |
Markdown Monster 1.16.16 | 368 | Friday, May 3, 2019 | Approved | |
Markdown Monster 1.16.15 | 300 | Tuesday, April 30, 2019 | Approved | |
Markdown Monster 1.16.8 | 410 | Monday, April 22, 2019 | Approved | |
Markdown Monster 1.16.6 | 292 | Tuesday, April 16, 2019 | Approved | |
Markdown Monster 1.16.5 | 465 | Monday, April 1, 2019 | Approved | |
Markdown Monster 1.16.4 | 364 | Tuesday, March 26, 2019 | Approved | |
Markdown Monster 1.16 | 320 | Wednesday, March 20, 2019 | Approved | |
Markdown Monster 1.15.8 | 348 | Thursday, March 14, 2019 | Approved | |
Markdown Monster 1.15.6 | 420 | Tuesday, March 5, 2019 | Approved | |
Markdown Monster 1.15.4 | 444 | Tuesday, February 19, 2019 | Approved | |
Markdown Monster 1.15.3 | 419 | Monday, February 11, 2019 | Approved | |
Markdown Monster 1.14.15 | 341 | Thursday, January 31, 2019 | Approved | |
Markdown Monster 1.14.12 | 318 | Thursday, January 24, 2019 | Approved | |
Markdown Monster 1.14.10 | 334 | Friday, January 18, 2019 | Approved | |
Markdown Monster 1.14.9 | 365 | Wednesday, January 9, 2019 | Approved | |
Markdown Monster 1.14.8 | 242 | Monday, January 7, 2019 | Approved | |
Markdown Monster 1.14.7 | 235 | Friday, January 4, 2019 | Approved | |
Markdown Monster 1.14.6 | 282 | Monday, December 31, 2018 | Approved | |
Markdown Monster 1.14.5 | 338 | Wednesday, December 19, 2018 | Approved | |
Markdown Monster 1.14.4 | 236 | Wednesday, December 19, 2018 | Approved | |
Markdown Monster 1.14 | 365 | Wednesday, December 12, 2018 | Approved | |
Markdown Monster 1.13.14 | 385 | Monday, December 3, 2018 | Approved | |
Markdown Monster 1.13.12 | 415 | Tuesday, November 20, 2018 | Approved | |
Markdown Monster 1.13.10 | 382 | Tuesday, November 13, 2018 | Approved | |
Markdown Monster 1.13.9 | 333 | Tuesday, November 6, 2018 | Approved | |
Markdown Monster 1.13.8 | 294 | Thursday, November 1, 2018 | Approved | |
Markdown Monster 1.13.7 | 373 | Thursday, October 25, 2018 | Approved | |
Markdown Monster 1.13.6 | 385 | Monday, October 15, 2018 | Approved | |
Markdown Monster 1.13.5 | 405 | Friday, October 5, 2018 | Approved | |
Markdown Monster 1.13 | 349 | Friday, September 28, 2018 | Approved | |
Markdown Monster 1.12.18 | 208 | Thursday, September 27, 2018 | Approved | |
Markdown Monster 1.12.17 | 275 | Sunday, September 23, 2018 | Approved | |
Markdown Monster 1.12.16 | 286 | Wednesday, September 19, 2018 | Approved | |
Markdown Monster 1.12.15 | 186 | Tuesday, September 18, 2018 | Approved | |
Markdown Monster 1.12.14.1 | 347 | Monday, September 10, 2018 | Approved | |
Markdown Monster 1.12.14 | 222 | Sunday, September 9, 2018 | Approved | |
Markdown Monster 1.12.12 | 489 | Thursday, August 16, 2018 | Approved | |
Markdown Monster 1.12.10 | 345 | Wednesday, August 8, 2018 | Approved | |
Markdown Monster 1.12.9 | 439 | Tuesday, July 24, 2018 | Approved | |
Markdown Monster 1.12.8 | 374 | Tuesday, July 17, 2018 | Approved | |
Markdown Monster 1.12.6 | 307 | Wednesday, July 11, 2018 | Approved | |
Markdown Monster 1.12.4 | 340 | Wednesday, July 4, 2018 | Approved | |
Markdown Monster 1.12 | 384 | Wednesday, June 27, 2018 | Approved | |
Markdown Monster 1.11.17 | 403 | Monday, June 18, 2018 | Approved | |
Markdown Monster 1.11.16 | 274 | Sunday, June 17, 2018 | Approved | |
Markdown Monster 1.11.15 | 307 | Monday, June 11, 2018 | Approved | |
Markdown Monster 1.11.14 | 217 | Monday, June 11, 2018 | Approved | |
Markdown Monster 1.11.12 | 292 | Thursday, June 7, 2018 | Approved | |
Markdown Monster 1.11.11 | 317 | Monday, June 4, 2018 | Approved | |
Markdown Monster 1.11.8 | 320 | Wednesday, May 30, 2018 | Approved | |
Markdown Monster 1.11.6 | 412 | Friday, May 25, 2018 | Approved | |
Markdown Monster 1.11.4 | 312 | Monday, May 21, 2018 | Approved | |
Markdown Monster 1.11.3 | 213 | Monday, May 21, 2018 | Approved | |
Markdown Monster 1.11 | 332 | Wednesday, May 16, 2018 | Approved | |
Markdown Monster 1.10.22 | 322 | Tuesday, May 15, 2018 | Approved | |
Markdown Monster 1.10.19 | 401 | Monday, May 7, 2018 | Approved | |
Markdown Monster 1.10.18 | 256 | Saturday, May 5, 2018 | Approved | |
Markdown Monster 1.10.16 | 360 | Monday, April 30, 2018 | Approved | |
Markdown Monster 1.10.7 | 395 | Tuesday, April 17, 2018 | Approved | |
Markdown Monster 1.10.5 | 461 | Friday, April 6, 2018 | Approved | |
Markdown Monster 1.10.4 | 343 | Wednesday, April 4, 2018 | Approved | |
Markdown Monster 1.10 | 356 | Wednesday, March 28, 2018 | Approved | |
Markdown Monster 1.9.18 | 382 | Wednesday, March 21, 2018 | Approved | |
Markdown Monster 1.9.16 | 267 | Tuesday, March 20, 2018 | Approved | |
Markdown Monster 1.9.4 | 506 | Thursday, February 15, 2018 | Approved | |
Markdown Monster 1.9.3 | 375 | Friday, February 9, 2018 | Approved | |
Markdown Monster 1.9.2 | 409 | Saturday, February 3, 2018 | Approved | |
Markdown Monster 1.9.0 | 411 | Wednesday, January 24, 2018 | Approved | |
Markdown Monster 1.8.15 | 381 | Tuesday, January 16, 2018 | Approved | |
Markdown Monster 1.8.14 | 370 | Friday, January 12, 2018 | Approved | |
Markdown Monster 1.8.12 | 358 | Tuesday, January 9, 2018 | Approved | |
Markdown Monster 1.8.10 | 405 | Tuesday, January 2, 2018 | Approved | |
Markdown Monster 1.8.9 | 394 | Saturday, December 30, 2017 | Approved | |
Markdown Monster 1.8.8 | 323 | Thursday, December 28, 2017 | Approved | |
Markdown Monster 1.8.4 | 363 | Wednesday, December 20, 2017 | Approved | |
Markdown Monster 1.8.2 | 460 | Saturday, December 9, 2017 | Approved | |
Markdown Monster 1.8.0 | 341 | Monday, December 4, 2017 | Approved | |
Markdown Monster 1.7.8 | 403 | Tuesday, November 28, 2017 | Approved | |
Markdown Monster 1.7.7 | 377 | Thursday, November 23, 2017 | Approved | |
Markdown Monster 1.7.6 | 340 | Monday, November 20, 2017 | Approved | |
Markdown Monster 1.7.4 | 425 | Wednesday, November 15, 2017 | Approved | |
Markdown Monster 1.7.2 | 417 | Monday, November 6, 2017 | Approved | |
Markdown Monster 1.7.0 | 499 | Thursday, October 19, 2017 | Approved | |
Markdown Monster 1.6.8 | 500 | Wednesday, October 11, 2017 | Approved | |
Markdown Monster 1.6.7 | 422 | Wednesday, October 4, 2017 | Approved | |
Markdown Monster 1.6.6 | 420 | Thursday, September 28, 2017 | Approved | |
Markdown Monster 1.6.5 | 416 | Thursday, September 21, 2017 | Approved | |
Markdown Monster 1.6.4 | 301 | Wednesday, September 20, 2017 | Approved | |
Markdown Monster 1.6.2 | 432 | Sunday, September 10, 2017 | Approved | |
Markdown Monster 1.6.0 | 372 | Wednesday, September 6, 2017 | Approved | |
Markdown Monster 1.5.12 | 342 | Friday, September 1, 2017 | Approved | |
Markdown Monster 1.5.8 | 387 | Thursday, August 24, 2017 | Approved | |
Markdown Monster 1.5.5 | 425 | Tuesday, August 15, 2017 | Approved | |
Markdown Monster 1.5.2 | 446 | Monday, August 7, 2017 | Approved | |
Markdown Monster 1.4.8 | 579 | Thursday, July 6, 2017 | Approved | |
Markdown Monster 1.4.5 | 435 | Tuesday, June 27, 2017 | Approved | |
Markdown Monster 1.4.3 | 459 | Saturday, June 17, 2017 | Approved | |
Markdown Monster 1.4 | 573 | Monday, June 12, 2017 | Approved | |
Markdown Monster 1.3.25 | 362 | Friday, June 9, 2017 | Approved | |
Markdown Monster 1.3.24 | 324 | Wednesday, June 7, 2017 | Approved | |
Markdown Monster 1.3.20 | 359 | Tuesday, May 30, 2017 | Approved | |
Markdown Monster 1.3.16 | 400 | Monday, May 22, 2017 | Approved | |
Markdown Monster 1.3.14 | 401 | Thursday, May 18, 2017 | Approved | |
Markdown Monster 1.3.11 | 340 | Tuesday, May 16, 2017 | Approved | |
Markdown Monster 1.3.10 | 387 | Saturday, May 13, 2017 | Approved | |
Markdown Monster 1.3.8 | 362 | Thursday, May 11, 2017 | Approved | |
Markdown Monster 1.3.7 | 389 | Tuesday, May 9, 2017 | Approved | |
Markdown Monster 1.3.5 | 370 | Saturday, May 6, 2017 | Approved | |
Markdown Monster 1.3.3 | 360 | Monday, May 1, 2017 | Approved | |
Markdown Monster 1.3.2 | 330 | Friday, April 28, 2017 | Approved | |
Markdown Monster 1.3 | 446 | Monday, April 17, 2017 | Approved | |
Markdown Monster 1.2.22 | 351 | Friday, April 14, 2017 | Approved | |
Markdown Monster 1.2.20 | 355 | Friday, April 7, 2017 | Approved | |
Markdown Monster 1.2.19 | 415 | Wednesday, April 5, 2017 | Approved | |
Markdown Monster 1.2.18 | 388 | Friday, March 31, 2017 | Approved | |
Markdown Monster 1.2.17 | 355 | Thursday, March 30, 2017 | Approved | |
Markdown Monster 1.2.16 | 451 | Thursday, March 23, 2017 | Approved | |
Markdown Monster 1.2.15 | 367 | Thursday, March 23, 2017 | Approved | |
Markdown Monster 1.2.14 | 435 | Monday, March 13, 2017 | Approved | |
Markdown Monster 1.2.10 | 405 | Tuesday, March 7, 2017 | Approved | |
Markdown Monster 1.2.8 | 446 | Tuesday, February 28, 2017 | Approved | |
Markdown Monster 1.2 | 383 | Wednesday, February 22, 2017 | Approved | |
Markdown Monster 1.1.30 | 379 | Thursday, February 16, 2017 | Approved | |
Markdown Monster 1.1.28 | 401 | Monday, February 13, 2017 | Approved | |
Markdown Monster 1.1.27 | 371 | Saturday, February 11, 2017 | Approved | |
Markdown Monster 1.1.26 | 376 | Friday, February 10, 2017 | Approved | |
Markdown Monster 1.1.24 | 439 | Thursday, February 2, 2017 | Approved | |
Markdown Monster 1.1.23 | 434 | Tuesday, January 31, 2017 | Approved | |
Markdown Monster 1.1.22 | 349 | Monday, January 30, 2017 | Approved | |
Markdown Monster 1.1.20 | 390 | Tuesday, January 24, 2017 | Approved | |
Markdown Monster 1.1.18 | 379 | Saturday, January 21, 2017 | Approved | |
Markdown Monster 1.1.16 | 382 | Thursday, January 19, 2017 | Approved | |
Markdown Monster 1.1.14 | 371 | Thursday, January 12, 2017 | Approved | |
Markdown Monster 1.1.12 | 396 | Tuesday, January 10, 2017 | Approved | |
Markdown Monster 1.1.8 | 439 | Saturday, January 7, 2017 | Approved | |
Markdown Monster 1.1 | 471 | Monday, January 2, 2017 | Approved | |
Markdown Monster 1.0.33 | 383 | Wednesday, December 28, 2016 | Approved | |
Markdown Monster 1.0.30 | 387 | Tuesday, December 20, 2016 | Approved | |
Markdown Monster 1.0.28 | 396 | Friday, December 16, 2016 | Approved | |
Markdown Monster 1.0.27 | 389 | Wednesday, December 14, 2016 | Approved | |
Markdown Monster 1.0.26 | 357 | Tuesday, December 13, 2016 | Approved | |
Markdown Monster 1.0.22 | 381 | Wednesday, December 7, 2016 | Approved | |
Markdown Monster 1.0.21 | 329 | Tuesday, December 6, 2016 | Approved | |
Markdown Monster 1.0.20 | 326 | Saturday, December 3, 2016 | Approved | |
Markdown Monster 1.0.19 | 398 | Wednesday, November 30, 2016 | Approved | |
Markdown Monster 1.0.18 | 380 | Monday, November 28, 2016 | Approved | |
Markdown Monster 1.0.14 | 396 | Friday, November 25, 2016 | Approved | |
Markdown Monster 1.0.10 | 344 | Tuesday, November 22, 2016 | Approved | |
Markdown Monster 1.0.9 | 388 | Friday, November 18, 2016 | Approved | |
Markdown Monster 1.0.7 | 443 | Tuesday, November 15, 2016 | Approved | |
Markdown Monster 1.0.6 | 364 | Sunday, November 13, 2016 | Approved | |
Markdown Monster 1.0.3 | 344 | Tuesday, November 8, 2016 | Approved | |
Markdown Monster 1.0.1 | 434 | Friday, November 4, 2016 | Approved |
West Wind Technologies, 2016-2021
This package has no dependencies.
Ground Rules:
- This discussion is only about Markdown Monster and the Markdown Monster package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Markdown Monster, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.