Step 1: Review Your Packages

Step 2: Choose Your Integration Method

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

Option 2: Internalized Package (Reliable, Scalable)

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

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:

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 ###

#### 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.2.4.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.2.4.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.2.4.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.2.4.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

Downloads:

41,959

Downloads of v 2.4-alpha-807:

133

Last Update:

14 Sep 2021

Package Maintainer(s):

Software Author(s):

Mixxx Development Team

Tags:

dj audio mixing party mp3 media cross-platform foss admin

Mixxx

This is a prerelease version of Mixxx.

2.4-alpha-807 | Updated: 14 Sep 2021

Downloads:

41,959

Downloads of v 2.4-alpha-807:

133

Maintainer(s):

Software Author(s):

Mixxx Development Team

Tags:

dj audio mixing party mp3 media cross-platform foss admin

Mixxx 2.4-alpha-807

This is a prerelease version of Mixxx.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Mixxx Development Team. The inclusion of Mixxx Development Team trademark(s), if any, upon this webpage is solely to identify Mixxx Development Team goods or services and not for commercial purposes.

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Mixxx, run the following command from the command line or from PowerShell:

To upgrade Mixxx, run the following command from the command line or from PowerShell:

To uninstall Mixxx, run the following command from the command line or from PowerShell:

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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download mixxx --internalize --version=2.4-alpha-807 --pre --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade mixxx -y --source="'INTERNAL REPO URL'" --version="'2.4-alpha-807'" --prerelease [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 mixxx -y --source="'INTERNAL REPO URL'" --version="'2.4-alpha-807'" --prerelease
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install mixxx
  win_chocolatey:
    name: mixxx
    version: '2.4-alpha-807'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'mixxx' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.4-alpha-807'
  options  '--prerelease'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller mixxx
{
    Name        = "mixxx"
    Version     = "2.4-alpha-807"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'mixxx':
  ensure          => '2.4-alpha-807',
  install_options => ['--prerelease'],
  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.

Package Approved

This package was approved as a trusted package on 14 Sep 2021.

Description

Mixxx is free DJ software for Windows, Mac OS X and Linux. It's easy to use so you can start mixing your favorite songs in no time, even if you've never DJed before. Mixxx offers a variety of features for experienced DJs and beginners alike, such as automatic beat and key detection, master sync, hotcues, looping, 4 decks, effects and many more. You can perform with Mixxx using MIDI and HID controllers, CD players, vinyl turntables or even just your computer's keyboard and mouse.

Features

Four Decks, Advanced Controls
- Time Stretch and Vinyl Emulation
- Beat Looping
- Powerful Master Sync
- Hotcues
- Beat Rolls and Censor
- Intuitive Pitchbend
- Broad Format Support
- EQ and Crossfader Control
- Built-in Effects
Organization
- Crates and PlaylistsFree Timecode Vinyl Control
- Disk Browsing
- iTunes and Traktor Library Integration
- MusicBrainz Tag Lookup
BPM Detection and Sync
Auto DJ
Record and Broadcast
- Recording
- Live Broadcasting
- ReplayGain Normalization
- Quad Microphone Input
DJ Controller Support
Free Timecode Vinyl Control

Files

legal\LICENSE.txt

                    GNU GENERAL PUBLIC LICENSE
                       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

                    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

                            NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, 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 THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

                     END OF TERMS AND CONDITIONS

            How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License along
    with this program; if not, write to the Free Software Foundation, Inc.,
    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

legal\VERIFICATION.txt

VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to <https://www.mixxx.org/download>

   x32: No longer being provided
   x64: https://downloads.mixxx.org/snapshots/main/mixxx-2.4-alpha-807-gf6872592ad-win64.msi

   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum64: 72A4F2DFF9CEE288978D232BF3A0E060C3D240195CB3CD5FA58024FF582BB033

File 'license.txt' is obtained from:
   https://www.gnu.org/licenses/gpl-2.0.html

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

if ((Get-OSArchitectureWidth 32) -or ($env:chocolateyForceX86 -eq 'true')) {
  throw "$env:ChocolateyPackageName do not provide 32bit installer anymore. Please use version 2.2.4 or lower."
}

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  fileType       = 'msi'
  file64         = "$toolsPath\mixxx-2.4-alpha-807-gf6872592ad-win64.msi"

  softwareName   = 'Mixxx *'

  silentArgs     = "/qn /norestart /l*v `"$($env:TEMP)\$($env:chocolateyPackageName).$($env:chocolateyPackageVersion).MsiInstall.log`""
  validExitCodes = @(0, 3010, 1641)
}

Install-ChocolateyInstallPackage @packageArgs

tools\mixxx-2.4-alpha-807-gf6872592ad-win64.msi

md5: 20A657ECAFA2A16E0A6126D893BA6B87 | sha1: 7737614627965D743607A7E5A6B70E9B18B8F1CB | sha256: 72A4F2DFF9CEE288978D232BF3A0E060C3D240195CB3CD5FA58024FF582BB033 | sha512: D99E080DFD70CC7A07A52574957B8D661E2037CFC67963840DB78B6E7C3D132C8071989E141A95D8994DF82891670EACCEB98A9EECDD9BBABAE1FEB2B08DD18B

Virus Scan Results

mixxx.2.4-alpha-807.nupkg (b323b55fd9d9) - ## / 56
mixxx-2.4-alpha-807-gf6872592ad-win64.msi (72a4f2dff9ce) - ## / 57

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.

Version History

Version	Downloads	Last Updated	Status
Mixxx 2.6.0-alpha-99	30	Monday, October 7, 2024	Approved
Mixxx 2.6.0-alpha-98	21	Wednesday, October 2, 2024	Approved
Mixxx 2.6.0-alpha-97	12	Tuesday, October 1, 2024	Approved
Mixxx 2.6.0-alpha-95	17	Friday, September 27, 2024	Approved
Mixxx 2.6.0-alpha-94	17	Thursday, September 26, 2024	Approved
Mixxx 2.6.0-alpha-93	39	Tuesday, September 24, 2024	Approved
Mixxx 2.6.0-alpha-92	20	Monday, September 23, 2024	Approved
Mixxx 2.6.0-alpha-91	19	Sunday, September 22, 2024	Approved
Mixxx 2.6.0-alpha-90	22	Thursday, September 19, 2024	Approved
Mixxx 2.6.0-alpha-88	25	Monday, September 16, 2024	Approved
Mixxx 2.6.0-alpha-87	28	Monday, September 16, 2024	Approved
Mixxx 2.6.0-alpha-86	24	Monday, September 16, 2024	Approved
Mixxx 2.6.0-alpha-85	24	Sunday, September 15, 2024	Approved
Mixxx 2.6.0-alpha-84	21	Saturday, September 7, 2024	Approved
Mixxx 2.6.0-alpha-83	26	Tuesday, September 3, 2024	Approved
Mixxx 2.6.0-alpha-82	19	Tuesday, September 3, 2024	Approved
Mixxx 2.6.0-alpha-81	19	Saturday, August 31, 2024	Approved
Mixxx 2.6.0-alpha-80	27	Friday, August 30, 2024	Approved
Mixxx 2.6.0-alpha-79	23	Friday, August 30, 2024	Approved
Mixxx 2.6.0-alpha-77	14	Thursday, August 29, 2024	Approved
Mixxx 2.6.0-alpha-76	32	Wednesday, August 28, 2024	Approved
Mixxx 2.6.0-alpha-75	28	Tuesday, August 27, 2024	Approved
Mixxx 2.6.0-alpha-74	21	Monday, August 26, 2024	Approved
Mixxx 2.6.0-alpha-73	21	Monday, August 26, 2024	Approved
Mixxx 2.6.0-alpha-71	17	Sunday, August 25, 2024	Approved
Mixxx 2.6.0-alpha-69	18	Friday, August 23, 2024	Approved
Mixxx 2.6.0-alpha-68	22	Monday, August 19, 2024	Approved
Mixxx 2.6.0-alpha-67	24	Sunday, August 18, 2024	Approved
Mixxx 2.6.0-alpha-66	21	Saturday, August 17, 2024	Approved
Mixxx 2.6.0-alpha-65	16	Thursday, August 15, 2024	Exempted
Mixxx 2.6.0-alpha-64	23	Thursday, August 15, 2024	Approved
Mixxx 2.6.0-alpha-63	19	Wednesday, August 14, 2024	Approved
Mixxx 2.6.0-alpha-62	23	Tuesday, August 13, 2024	Approved
Mixxx 2.6.0-alpha-60	28	Monday, August 12, 2024	Approved
Mixxx 2.6.0-alpha-59	29	Saturday, August 10, 2024	Approved
Mixxx 2.6.0-alpha-58	19	Friday, August 9, 2024	Approved
Mixxx 2.6.0-alpha-57	25	Tuesday, August 6, 2024	Approved
Mixxx 2.6.0-alpha-56	26	Friday, August 2, 2024	Approved
Mixxx 2.6.0-alpha-55	28	Wednesday, July 31, 2024	Approved
Mixxx 2.6.0-alpha-54	28	Friday, July 26, 2024	Approved
Mixxx 2.6.0-alpha-53	34	Wednesday, July 24, 2024	Approved
Mixxx 2.6.0-alpha-51	23	Tuesday, July 23, 2024	Approved
Mixxx 2.6.0-alpha-48	26	Monday, July 22, 2024	Approved
Mixxx 2.6.0-alpha-47	26	Saturday, July 20, 2024	Approved
Mixxx 2.6.0-alpha-45	30	Friday, July 19, 2024	Approved
Mixxx 2.6.0-alpha-44	26	Tuesday, July 16, 2024	Approved
Mixxx 2.6.0-alpha-43	20	Monday, July 15, 2024	Approved
Mixxx 2.6.0-alpha-42	25	Monday, July 15, 2024	Approved
Mixxx 2.6.0-alpha-38	36	Sunday, July 14, 2024	Approved
Mixxx 2.6.0-alpha-37	23	Saturday, July 13, 2024	Approved
Mixxx 2.6.0-alpha-36	28	Thursday, July 11, 2024	Approved
Mixxx 2.6.0-alpha-35	30	Wednesday, July 10, 2024	Approved
Mixxx 2.6.0-alpha-33	35	Tuesday, July 9, 2024	Approved
Mixxx 2.6.0-alpha-32	26	Tuesday, July 9, 2024	Approved
Mixxx 2.6.0-alpha-30	30	Friday, July 5, 2024	Approved
Mixxx 2.6.0-alpha-29	28	Tuesday, July 2, 2024	Approved
Mixxx 2.6.0-alpha-28	22	Tuesday, July 2, 2024	Approved
Mixxx 2.6.0-alpha-27	30	Monday, July 1, 2024	Approved
Mixxx 2.6.0-alpha-26	29	Sunday, June 30, 2024	Approved
Mixxx 2.6.0-alpha-24	22	Friday, June 28, 2024	Approved
Mixxx 2.6.0-alpha-23	30	Tuesday, June 25, 2024	Approved
Mixxx 2.6.0-alpha-22	27	Tuesday, June 25, 2024	Approved
Mixxx 2.6.0-alpha-21	29	Wednesday, June 19, 2024	Approved
Mixxx 2.6.0-alpha-20	28	Tuesday, June 18, 2024	Approved
Mixxx 2.6.0-alpha-19	26	Monday, June 17, 2024	Approved
Mixxx 2.6.0-alpha-17	28	Sunday, June 16, 2024	Approved
Mixxx 2.6.0-alpha-16	26	Friday, June 14, 2024	Approved
Mixxx 2.6.0-alpha-15	30	Thursday, June 13, 2024	Approved
Mixxx 2.5.0-beta-88	5	Wednesday, November 20, 2024	Approved
Mixxx 2.5.0-beta-86	6	Monday, November 18, 2024	Approved
Mixxx 2.5.0-beta-85	5	Monday, November 18, 2024	Approved
Mixxx 2.5.0-beta-84	6	Saturday, November 16, 2024	Approved
Mixxx 2.5.0-beta-83	5	Saturday, November 16, 2024	Approved
Mixxx 2.5.0-beta-82	14	Monday, November 11, 2024	Approved
Mixxx 2.5.0-beta-79	14	Sunday, November 10, 2024	Approved
Mixxx 2.5.0-beta-78	14	Saturday, November 9, 2024	Approved
Mixxx 2.5.0-beta-77	14	Saturday, November 9, 2024	Approved
Mixxx 2.5.0-beta-76	12	Saturday, November 9, 2024	Approved
Mixxx 2.5.0-beta-75	13	Friday, November 8, 2024	Approved
Mixxx 2.5.0-beta-74	10	Tuesday, November 5, 2024	Approved
Mixxx 2.5.0-beta-68	11	Monday, October 21, 2024	Approved
Mixxx 2.5.0-beta-67	10	Sunday, October 20, 2024	Approved
Mixxx 2.5.0-beta-66	6	Sunday, October 20, 2024	Approved
Mixxx 2.5.0-beta-65	10	Saturday, October 19, 2024	Approved
Mixxx 2.5.0-beta-64	13	Tuesday, October 15, 2024	Approved
Mixxx 2.5.0-beta-63	15	Monday, October 14, 2024	Approved
Mixxx 2.5.0-beta-62	10	Saturday, October 12, 2024	Approved
Mixxx 2.5.0-beta-61	11	Thursday, October 10, 2024	Approved
Mixxx 2.5.0-beta-60	13	Wednesday, October 9, 2024	Approved
Mixxx 2.5.0-beta-59	15	Saturday, September 28, 2024	Approved
Mixxx 2.5.0-beta-58	16	Friday, September 27, 2024	Approved
Mixxx 2.5.0-beta-57	21	Wednesday, September 25, 2024	Approved
Mixxx 2.5.0-beta-56	17	Sunday, September 22, 2024	Approved
Mixxx 2.5.0-beta-55	20	Friday, September 20, 2024	Approved
Mixxx 2.5.0-beta-54	17	Thursday, September 19, 2024	Approved
Mixxx 2.5.0-beta-53	25	Wednesday, September 18, 2024	Approved
Mixxx 2.5.0-beta-52	23	Monday, September 16, 2024	Approved
Mixxx 2.5.0-beta-51	22	Sunday, September 15, 2024	Approved
Mixxx 2.5.0-beta-49	14	Sunday, September 8, 2024	Approved
Mixxx 2.5.0-beta-48	23	Friday, September 6, 2024	Approved
Mixxx 2.5.0-beta-47	20	Tuesday, September 3, 2024	Approved
Mixxx 2.5.0-beta-46	20	Friday, August 30, 2024	Approved
Mixxx 2.5.0-beta-44	18	Thursday, August 29, 2024	Approved
Mixxx 2.5.0-beta-43	19	Tuesday, August 20, 2024	Approved
Mixxx 2.5.0-beta-42	21	Tuesday, August 20, 2024	Approved
Mixxx 2.5.0-beta-41	19	Monday, August 19, 2024	Approved
Mixxx 2.5.0-beta-40	24	Monday, August 19, 2024	Approved
Mixxx 2.5.0-beta-39	24	Sunday, August 18, 2024	Approved
Mixxx 2.5.0-beta-38	20	Thursday, August 15, 2024	Exempted
Mixxx 2.5.0-beta-36	18	Wednesday, August 14, 2024	Approved
Mixxx 2.5.0-beta-35	21	Wednesday, August 14, 2024	Approved
Mixxx 2.5.0-beta-34	27	Monday, August 12, 2024	Approved
Mixxx 2.5.0-beta-33	13	Wednesday, August 7, 2024	Approved
Mixxx 2.5.0-beta-31	22	Tuesday, August 6, 2024	Approved
Mixxx 2.5.0-beta-30	21	Friday, August 2, 2024	Approved
Mixxx 2.5.0-beta-29	23	Thursday, August 1, 2024	Approved
Mixxx 2.5.0-beta-28	22	Thursday, July 25, 2024	Approved
Mixxx 2.5.0-beta-26	31	Tuesday, July 23, 2024	Approved
Mixxx 2.5.0-beta-25	24	Friday, July 19, 2024	Approved
Mixxx 2.5.0-beta-23	27	Monday, July 15, 2024	Approved
Mixxx 2.5.0-beta-21	25	Saturday, July 13, 2024	Approved
Mixxx 2.5.0-beta-20	28	Wednesday, July 10, 2024	Approved
Mixxx 2.5.0-beta-19	22	Monday, July 8, 2024	Approved
Mixxx 2.5.0-beta-16	31	Thursday, July 4, 2024	Approved
Mixxx 2.5.0-beta-15	31	Saturday, June 29, 2024	Approved
Mixxx 2.5.0-beta-13	32	Wednesday, June 26, 2024	Approved
Mixxx 2.5.0-beta-12	29	Tuesday, June 25, 2024	Approved
Mixxx 2.5.0-alpha-99	70	Sunday, September 10, 2023	Approved
Mixxx 2.5.0-alpha-97	53	Friday, September 8, 2023	Approved
Mixxx 2.5.0-alpha-95	41	Friday, September 8, 2023	Approved
Mixxx 2.5.0-alpha-93	64	Thursday, September 7, 2023	Approved
Mixxx 2.5.0-alpha-92	49	Wednesday, September 6, 2023	Approved
Mixxx 2.5.0-alpha-90	66	Tuesday, September 5, 2023	Approved
Mixxx 2.5.0-alpha-89	60	Tuesday, September 5, 2023	Approved
Mixxx 2.5.0-alpha-88	86	Sunday, September 3, 2023	Approved
Mixxx 2.5.0-alpha-87	54	Friday, September 1, 2023	Approved
Mixxx 2.5.0-alpha-86	86	Friday, September 1, 2023	Approved
Mixxx 2.5.0-alpha-85	53	Thursday, August 31, 2023	Approved
Mixxx 2.5.0-alpha-84	58	Thursday, August 31, 2023	Approved
Mixxx 2.5.0-alpha-79	68	Tuesday, August 29, 2023	Approved
Mixxx 2.5.0-alpha-77	68	Monday, August 28, 2023	Approved
Mixxx 2.5.0-alpha-76	59	Sunday, August 27, 2023	Approved
Mixxx 2.5.0-alpha-75	58	Saturday, August 26, 2023	Approved
Mixxx 2.5.0-alpha-74	57	Friday, August 25, 2023	Approved
Mixxx 2.5.0-alpha-73	64	Monday, August 21, 2023	Approved
Mixxx 2.5.0-alpha-72	69	Sunday, August 20, 2023	Approved
Mixxx 2.5.0-alpha-71	69	Friday, August 18, 2023	Approved
Mixxx 2.5.0-alpha-69	71	Monday, August 14, 2023	Approved
Mixxx 2.5.0-alpha-68	70	Sunday, August 6, 2023	Approved
Mixxx 2.5.0-alpha-67	699	Saturday, August 5, 2023	Approved
Mixxx 2.5.0-alpha-66	79	Thursday, August 3, 2023	Approved
Mixxx 2.5.0-alpha-65	71	Thursday, August 3, 2023	Approved
Mixxx 2.5.0-alpha-64	75	Friday, July 28, 2023	Approved
Mixxx 2.5.0-alpha-63	96	Tuesday, July 11, 2023	Approved
Mixxx 2.5.0-alpha-62	73	Monday, July 10, 2023	Approved
Mixxx 2.5.0-alpha-61	70	Monday, July 10, 2023	Approved
Mixxx 2.5.0-alpha-60	70	Saturday, July 8, 2023	Approved
Mixxx 2.5.0-alpha-59	51	Tuesday, July 4, 2023	Approved
Mixxx 2.5.0-alpha-58	63	Sunday, July 2, 2023	Approved
Mixxx 2.5.0-alpha-56	92	Saturday, July 1, 2023	Approved
Mixxx 2.5.0-alpha-54	83	Wednesday, June 28, 2023	Approved
Mixxx 2.5.0-alpha-53	56	Monday, June 26, 2023	Approved
Mixxx 2.5.0-alpha-52	48	Monday, June 19, 2023	Approved
Mixxx 2.5.0-alpha-51	80	Saturday, June 17, 2023	Approved
Mixxx 2.5.0-alpha-50	67	Thursday, June 15, 2023	Approved
Mixxx 2.5.0-alpha-49	51	Wednesday, June 14, 2023	Approved
Mixxx 2.5.0-alpha-48	49	Sunday, June 11, 2023	Approved
Mixxx 2.5-alpha-47	92	Tuesday, June 6, 2023	Approved
Mixxx 2.5-alpha-44	65	Monday, June 5, 2023	Approved
Mixxx 2.5-alpha-43	58	Saturday, June 3, 2023	Approved
Mixxx 2.5-alpha-42	81	Tuesday, May 30, 2023	Approved
Mixxx 2.5-alpha-40	82	Monday, May 29, 2023	Approved
Mixxx 2.5-alpha-39	52	Tuesday, May 23, 2023	Approved
Mixxx 2.5-alpha-38	70	Monday, May 22, 2023	Approved
Mixxx 2.5-alpha-37	75	Wednesday, May 17, 2023	Approved
Mixxx 2.5-alpha-36	51	Tuesday, May 16, 2023	Approved
Mixxx 2.5-alpha-33	57	Saturday, May 13, 2023	Approved
Mixxx 2.5-alpha-32	72	Friday, May 12, 2023	Approved
Mixxx 2.5-alpha-31	73	Tuesday, May 9, 2023	Approved
Mixxx 2.5-alpha-30	65	Friday, May 5, 2023	Approved
Mixxx 2.5-alpha-29	94	Saturday, April 29, 2023	Approved
Mixxx 2.5-alpha-26	59	Tuesday, April 18, 2023	Approved
Mixxx 2.4.1	693	Saturday, May 11, 2024	Approved
Mixxx 2.4.0	535	Saturday, February 17, 2024	Approved
Mixxx 2.4.0-beta-99	63	Sunday, August 27, 2023	Approved
Mixxx 2.4.0-beta-98	55	Sunday, August 27, 2023	Approved
Mixxx 2.4.0-beta-97	86	Saturday, August 26, 2023	Approved
Mixxx 2.4.0-beta-96	57	Thursday, August 24, 2023	Approved
Mixxx 2.4.0-beta-95	50	Tuesday, August 22, 2023	Approved
Mixxx 2.4.0-beta-94	80	Monday, August 21, 2023	Approved
Mixxx 2.4.0-beta-93	55	Saturday, August 19, 2023	Approved
Mixxx 2.4.0-beta-92	68	Friday, August 18, 2023	Approved
Mixxx 2.4.0-beta-90	57	Thursday, August 17, 2023	Approved
Mixxx 2.4.0-beta-89	48	Tuesday, August 15, 2023	Approved
Mixxx 2.4.0-beta-88	45	Sunday, August 13, 2023	Approved
Mixxx 2.4.0-beta-86	63	Sunday, August 13, 2023	Approved
Mixxx 2.4.0-beta-83	50	Friday, August 11, 2023	Approved
Mixxx 2.4.0-beta-82	75	Friday, August 11, 2023	Approved
Mixxx 2.4.0-beta-80	50	Thursday, August 10, 2023	Approved
Mixxx 2.4.0-beta-79	66	Wednesday, August 9, 2023	Exempted
Mixxx 2.4.0-beta-78	79	Tuesday, August 8, 2023	Approved
Mixxx 2.4.0-beta-77	72	Monday, August 7, 2023	Approved
Mixxx 2.4.0-beta-75	58	Sunday, August 6, 2023	Approved
Mixxx 2.4.0-beta-74	101	Sunday, August 6, 2023	Approved
Mixxx 2.4.0-beta-73	89	Saturday, August 5, 2023	Approved
Mixxx 2.4.0-beta-72	80	Thursday, August 3, 2023	Approved
Mixxx 2.4.0-beta-71	66	Thursday, August 3, 2023	Approved
Mixxx 2.4.0-beta-70	88	Thursday, August 3, 2023	Approved
Mixxx 2.4-beta-7	68	Sunday, June 4, 2023	Approved
Mixxx 2.4-beta-6	49	Sunday, June 4, 2023	Approved
Mixxx 2.4-beta-5	71	Friday, June 2, 2023	Approved
Mixxx 2.4-beta-4	77	Thursday, June 1, 2023	Approved
Mixxx 2.4-beta-3	48	Wednesday, May 31, 2023	Approved
Mixxx 2.4-alpha-999	176	Monday, November 22, 2021	Approved
Mixxx 2.4-alpha-998	118	Monday, November 22, 2021	Approved
Mixxx 2.4-alpha-996	102	Sunday, November 21, 2021	Approved
Mixxx 2.4-alpha-995	117	Saturday, November 20, 2021	Approved
Mixxx 2.4-alpha-994	133	Saturday, November 20, 2021	Approved
Mixxx 2.4-alpha-992	104	Thursday, November 18, 2021	Approved
Mixxx 2.4-alpha-991	105	Wednesday, November 17, 2021	Approved
Mixxx 2.4-alpha-989	116	Tuesday, November 16, 2021	Approved
Mixxx 2.4-alpha-988	120	Sunday, November 14, 2021	Approved
Mixxx 2.4-alpha-985	138	Saturday, November 13, 2021	Approved
Mixxx 2.4-alpha-983	139	Friday, November 12, 2021	Approved
Mixxx 2.4-alpha-982	108	Thursday, November 11, 2021	Approved
Mixxx 2.4-alpha-981	108	Wednesday, November 10, 2021	Approved
Mixxx 2.4-alpha-980	101	Tuesday, November 9, 2021	Approved
Mixxx 2.4-alpha-979	140	Monday, November 8, 2021	Approved
Mixxx 2.4-alpha-977	133	Sunday, November 7, 2021	Approved
Mixxx 2.4-alpha-975	116	Saturday, November 6, 2021	Approved
Mixxx 2.4-alpha-972	115	Wednesday, November 3, 2021	Approved
Mixxx 2.4-alpha-971	120	Tuesday, November 2, 2021	Approved
Mixxx 2.4-alpha-970	133	Saturday, October 30, 2021	Approved
Mixxx 2.4-alpha-969	134	Friday, October 29, 2021	Approved
Mixxx 2.4-alpha-967	135	Thursday, October 28, 2021	Approved
Mixxx 2.4-alpha-966	110	Tuesday, October 26, 2021	Approved
Mixxx 2.4-alpha-965	129	Tuesday, October 26, 2021	Approved
Mixxx 2.4-alpha-964	99	Tuesday, October 26, 2021	Approved
Mixxx 2.4-alpha-962	117	Monday, October 25, 2021	Approved
Mixxx 2.4-alpha-961	127	Monday, October 25, 2021	Approved
Mixxx 2.4-alpha-959	99	Sunday, October 24, 2021	Exempted
Mixxx 2.4-alpha-957	146	Sunday, October 24, 2021	Approved
Mixxx 2.4-alpha-956	130	Sunday, October 24, 2021	Approved
Mixxx 2.4-alpha-955	140	Saturday, October 23, 2021	Approved
Mixxx 2.4-alpha-953	121	Thursday, October 21, 2021	Approved
Mixxx 2.4-alpha-952	100	Thursday, October 21, 2021	Approved
Mixxx 2.4-alpha-950	113	Wednesday, October 20, 2021	Approved
Mixxx 2.4-alpha-947	158	Monday, October 18, 2021	Approved
Mixxx 2.4-alpha-946	121	Monday, October 18, 2021	Approved
Mixxx 2.4-alpha-942	131	Sunday, October 17, 2021	Approved
Mixxx 2.4-alpha-939	138	Sunday, October 17, 2021	Approved
Mixxx 2.4-alpha-934	130	Sunday, October 17, 2021	Approved
Mixxx 2.4-alpha-928	128	Sunday, October 17, 2021	Approved
Mixxx 2.4-alpha-925	145	Saturday, October 16, 2021	Approved
Mixxx 2.4-alpha-924	136	Friday, October 15, 2021	Approved
Mixxx 2.4-alpha-922	122	Friday, October 15, 2021	Approved
Mixxx 2.4-alpha-920	108	Friday, October 15, 2021	Approved
Mixxx 2.4-alpha-919	104	Friday, October 15, 2021	Approved
Mixxx 2.4-alpha-915	147	Thursday, October 14, 2021	Approved
Mixxx 2.4-alpha-913	112	Thursday, October 14, 2021	Approved
Mixxx 2.4-alpha-911	122	Thursday, October 14, 2021	Approved
Mixxx 2.4-alpha-906	126	Wednesday, October 13, 2021	Approved
Mixxx 2.4-alpha-892	150	Wednesday, October 13, 2021	Exempted
Mixxx 2.4-alpha-889	103	Wednesday, October 13, 2021	Approved
Mixxx 2.4-alpha-880	148	Tuesday, October 12, 2021	Approved
Mixxx 2.4-alpha-877	116	Tuesday, October 12, 2021	Approved
Mixxx 2.4-alpha-876	157	Monday, October 11, 2021	Approved
Mixxx 2.4-alpha-875	114	Monday, October 11, 2021	Approved
Mixxx 2.4-alpha-874	105	Sunday, October 10, 2021	Approved
Mixxx 2.4-alpha-873	150	Sunday, October 10, 2021	Approved
Mixxx 2.4-alpha-872	109	Saturday, October 9, 2021	Approved
Mixxx 2.4-alpha-871	119	Saturday, October 9, 2021	Approved
Mixxx 2.4-alpha-870	138	Friday, October 8, 2021	Approved
Mixxx 2.4-alpha-868	137	Thursday, October 7, 2021	Approved
Mixxx 2.4-alpha-866	100	Wednesday, October 6, 2021	Approved
Mixxx 2.4-alpha-864	125	Tuesday, October 5, 2021	Approved
Mixxx 2.4-alpha-861	97	Sunday, October 3, 2021	Approved
Mixxx 2.4-alpha-860	123	Friday, October 1, 2021	Approved
Mixxx 2.4-alpha-859	112	Friday, October 1, 2021	Approved
Mixxx 2.4-alpha-856	128	Thursday, September 30, 2021	Approved
Mixxx 2.4-alpha-855	170	Thursday, September 30, 2021	Approved
Mixxx 2.4-alpha-850	121	Wednesday, September 29, 2021	Approved
Mixxx 2.4-alpha-849	110	Wednesday, September 29, 2021	Approved
Mixxx 2.4-alpha-848	138	Tuesday, September 28, 2021	Approved
Mixxx 2.4-alpha-847	120	Monday, September 27, 2021	Approved
Mixxx 2.4-alpha-846	107	Monday, September 27, 2021	Approved
Mixxx 2.4-alpha-845	127	Thursday, September 23, 2021	Approved
Mixxx 2.4-alpha-842	126	Wednesday, September 22, 2021	Approved
Mixxx 2.4-alpha-841	110	Wednesday, September 22, 2021	Exempted
Mixxx 2.4-alpha-840	158	Monday, September 20, 2021	Approved
Mixxx 2.4-alpha-839	164	Monday, September 20, 2021	Approved
Mixxx 2.4-alpha-837	116	Monday, September 20, 2021	Approved
Mixxx 2.4-alpha-836	117	Sunday, September 19, 2021	Approved
Mixxx 2.4-alpha-835	128	Sunday, September 19, 2021	Approved
Mixxx 2.4-alpha-832	119	Sunday, September 19, 2021	Approved
Mixxx 2.4-alpha-827	99	Sunday, September 19, 2021	Approved
Mixxx 2.4-alpha-824	131	Saturday, September 18, 2021	Approved
Mixxx 2.4-alpha-821	124	Saturday, September 18, 2021	Approved
Mixxx 2.4-alpha-817	115	Friday, September 17, 2021	Approved
Mixxx 2.4-alpha-816	162	Thursday, September 16, 2021	Approved
Mixxx 2.4-alpha-815	163	Thursday, September 16, 2021	Approved
Mixxx 2.4-alpha-814	131	Wednesday, September 15, 2021	Approved
Mixxx 2.4-alpha-811	104	Wednesday, September 15, 2021	Exempted
Mixxx 2.4-alpha-807	133	Tuesday, September 14, 2021	Approved
Mixxx 2.4-alpha-806	148	Monday, September 13, 2021	Approved
Mixxx 2.4-alpha-805	118	Monday, September 13, 2021	Approved
Mixxx 2.4-alpha-804	151	Friday, September 10, 2021	Approved
Mixxx 2.4-alpha-803	135	Thursday, September 9, 2021	Approved
Mixxx 2.4-alpha-801	128	Thursday, September 9, 2021	Approved
Mixxx 2.4-alpha-799	137	Wednesday, September 8, 2021	Approved
Mixxx 2.4-alpha-793	140	Tuesday, September 7, 2021	Approved
Mixxx 2.4-alpha-792	147	Tuesday, September 7, 2021	Approved
Mixxx 2.4-alpha-791	120	Tuesday, September 7, 2021	Approved
Mixxx 2.4-alpha-790	144	Sunday, September 5, 2021	Approved
Mixxx 2.4-alpha-789	118	Sunday, September 5, 2021	Approved
Mixxx 2.4-alpha-788	123	Saturday, September 4, 2021	Approved
Mixxx 2.4-alpha-786	169	Saturday, September 4, 2021	Approved
Mixxx 2.4-alpha-785	135	Thursday, September 2, 2021	Approved
Mixxx 2.4-alpha-783	151	Sunday, August 29, 2021	Approved
Mixxx 2.4-alpha-782	117	Sunday, August 29, 2021	Approved
Mixxx 2.4-alpha-780	139	Sunday, August 29, 2021	Approved
Mixxx 2.4-alpha-779	143	Saturday, August 28, 2021	Approved
Mixxx 2.4-alpha-776	147	Wednesday, August 25, 2021	Approved
Mixxx 2.4-alpha-775	94	Tuesday, August 24, 2021	Approved
Mixxx 2.4-alpha-774	158	Sunday, August 22, 2021	Exempted
Mixxx 2.4-alpha-773	132	Saturday, August 21, 2021	Approved
Mixxx 2.4-alpha-772	130	Saturday, August 21, 2021	Approved
Mixxx 2.4-alpha-769	141	Friday, August 20, 2021	Approved
Mixxx 2.4-alpha-767	158	Thursday, August 19, 2021	Approved
Mixxx 2.4-alpha-761	147	Wednesday, August 18, 2021	Approved
Mixxx 2.4-alpha-760	152	Wednesday, August 18, 2021	Approved
Mixxx 2.4-alpha-758	146	Wednesday, August 18, 2021	Approved
Mixxx 2.4-alpha-755	140	Tuesday, August 17, 2021	Approved
Mixxx 2.4-alpha-753	130	Tuesday, August 17, 2021	Approved
Mixxx 2.4-alpha-749	143	Monday, August 16, 2021	Approved
Mixxx 2.4-alpha-748	208	Friday, August 13, 2021	Approved
Mixxx 2.4-alpha-747	177	Friday, August 13, 2021	Approved
Mixxx 2.4-alpha-744	138	Wednesday, August 11, 2021	Approved
Mixxx 2.4-alpha-743	144	Monday, August 9, 2021	Approved
Mixxx 2.4-alpha-741	136	Sunday, August 8, 2021	Approved
Mixxx 2.4-alpha-740	118	Sunday, August 8, 2021	Approved
Mixxx 2.4-alpha-739	129	Saturday, August 7, 2021	Approved
Mixxx 2.3.6	659	Tuesday, August 15, 2023	Approved
Mixxx 2.3.5	536	Thursday, May 11, 2023	Approved
Mixxx 2.3.4	413	Friday, March 3, 2023	Approved
Mixxx 2.3.3	827	Wednesday, June 22, 2022	Approved
Mixxx 2.3.2	536	Tuesday, February 1, 2022	Approved
Mixxx 2.3.1	524	Friday, October 1, 2021	Approved
Mixxx 2.3.0	383	Saturday, August 7, 2021	Approved
Mixxx 2.2.4	1157	Friday, June 26, 2020	Approved
Mixxx 2.2.3	929	Monday, December 9, 2019	Approved
Mixxx 2.2.2	634	Thursday, August 15, 2019	Approved
Mixxx 2.2.1	620	Wednesday, April 24, 2019	Approved
Mixxx 2.2.0	722	Friday, January 11, 2019	Approved
Mixxx 2.1.5	859	Wednesday, October 31, 2018	Approved
Mixxx 2.1.4	1206	Tuesday, September 11, 2018	Approved
Mixxx 2.1.3	563	Monday, September 3, 2018	Approved
Mixxx 2.1.0-rc1	454	Monday, April 9, 2018	Exempted
Mixxx 2.0.0.20180111	719	Thursday, January 11, 2018	Approved
Mixxx 2.0.0.20161110	766	Thursday, November 10, 2016	Approved
Mixxx 2.0.0	601	Wednesday, December 30, 2015	Approved
Mixxx 1.11.0	872	Friday, May 10, 2013	Unknown
Mixxx 1.10.1	561	Saturday, April 27, 2013	Unknown

Release Notes

http://mixxxblog.blogspot.it/

Dependencies

- kb2999226 (≥ 1.0.20181019)

Discussion for the Mixxx Package

Ground Rules:

This discussion is only about Mixxx and the Mixxx 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 Mixxx, 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.

Resources

Events

Courses

41,959

133

14 Sep 2021

Mixxx

Mixxx 2.4-alpha-807

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Features

Ground Rules: