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.1.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.1.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.1.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.1.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:

21

Downloads of v 24.10.0:

14

Last Update:

14 Nov 2024

Package Maintainer(s):

EventStoreDB

Software Author(s):

EventStore

Tags:

eventstore database eventsourcing

EventStore

24.10.0 | Updated: 14 Nov 2024

Downloads:

Downloads of v 24.10.0:

Maintainer(s):

EventStoreDB

Software Author(s):

EventStore

Tags:

eventstore database eventsourcing

EventStore 24.10.0

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

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

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

To uninstall EventStore, 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 eventstoredb-ee --internalize --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 eventstoredb-ee -y --source="'INTERNAL REPO URL'" [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 eventstoredb-ee -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install eventstoredb-ee
  win_chocolatey:
    name: eventstoredb-ee
    version: '24.10.0'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'eventstoredb-ee' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '24.10.0'
end

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


cChocoPackageInstaller eventstoredb-ee
{
    Name     = "eventstoredb-ee"
    Version  = "24.10.0"
    Source   = "INTERNAL REPO URL"
}

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


package { 'eventstoredb-ee':
  ensure   => '24.10.0',
  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.

WARNING

There are versions of this package awaiting moderation . See the Version History section below.

Package Approved

This package was approved by moderator flcdrg on 10 Dec 2024.

Description

EventStoreDB is a new category of operational database that has evolved from the Event Sourcing community. Powered by the state-transition data model, events are stored with the context of why they have happened. Providing flexible, real-time data insights in the language your business understands.

Files

chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';

$packageName = 'eventstoredb-ee'
$destinationDir    = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)\eventstoredb-24.10.0-ee-windows.x64"
$zipFile     = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)\eventstoredb-24.10.0-ee-windows.x64.zip"

$packageArgs = @{
  packageName    = $packageName
  destination    = $destinationDir
  fileFullPath   = $zipFile
}

Get-ChocolateyUnzip @packageArgs

Write-Output "Output to $toolsDir"

chocolateyuninstall.ps1

$ErrorActionPreference = 'Stop';

$packageName = 'eventstoredb-ee'
$zipFileName = 'eventstoredb-24.10.0-ee-windows.x64.zip'

Uninstall-ChocolateyZipPackage -PackageName $packageName -ZipFileName $zipFileName

eventstoredb-24.10.0-ee-windows.x64.zip

md5: C1D473C82F60BB3292A4ED2B15B33AE8 | sha1: 8F74BD6D16779187F4B3F0BE1D1C6AA3128528F6 | sha256: D8B1CC8DE44CA4F7587D83DF4E6151398CD820F0289D7462F19D83F4FD989486 | sha512: 73ADDA49EA587748E0682D2FA269FD59EFFC7249AF572CF107F356645F488B5230A633D16C3616F453CD8567ADE47C17F60914B757789D2084CB8A2EAF211D4C

LICENSE.md

# Event Store License v2

Copyright (c) 2011-2024, Event Store Ltd. All rights reserved.

### Acceptance

By using the software, you agree to all of the terms and conditions below.

### Copyright License

The licensor grants you a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the software, in each case subject to the limitations and conditions below.

### Limitations

You may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the software.

Unless authorized in writing by the licensor, you may not move, change, disable, interfere with, or circumvent the license mechanisms in the software, and you may not remove or obscure any functionality in the software that is protected by the license mechanisms.

You may not alter, remove, or obscure any licensing, copyright, or other notices of the licensor in the software. Any use of the licensor’s trademarks is subject to applicable law.

### Patents

The licensor grants you a license, under any patent claims the licensor can license, or becomes able to license, to make, have made, use, sell, offer for sale, import and have imported the software, in each case subject to the limitations and conditions in this license. This license does not cover any patent claims that you cause to be infringed by modifications or additions to the software. If you or your company make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.

### Notices

You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms.

If you modify the software, you must include in any modified copies of the software prominent notices stating that you have modified the software.

### No Other Rights

These terms do not imply any licenses other than those expressly granted in these terms.

### Termination

If you use the software in violation of these terms, such use is not licensed, and your licenses will automatically terminate. If the licensor provides you with a notice of your violation, and you cease all violation of this license no later than 30 days after you receive that notice, your licenses will be reinstated retroactively. However, if you violate these terms after such reinstatement, any additional violation of these terms will cause your licenses to terminate automatically and permanently.

### No Liability

***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***

### Definitions

The **licensor** is the entity offering these terms, and the **software** is the software the licensor makes available under these terms, including any portion of it.

**licensing mechanisms** refers to functionality that restricts use of the software based on whether you possess a valid license key, including functionality to validate license keys and audit usage of the software to ensure license compliance.

**you** refers to the individual or entity agreeing to these terms.

**your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. **control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.

**your licenses** are all the licenses granted to you for the software under these terms.

**use** means anything you do with the software requiring one of your licenses.

**trademark** means trademarks, service marks, and similar rights.

LICENSE_CONTRIBUTIONS.md

EventStoreDB code after versions 24.6.x is generally subject to the terms of the
Event Store License v2 (ESLv2, see LICENSE.md), however, some parts of the code remain
subject to the terms of the Event Store License, which they were contributed under.

# Event Store License

Copyright (c) 2011-2024, Event Store Ltd. and Contributors. All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.

Neither the name of Event Store Ltd nor the names of its contributors may be
used to endorse or promote products derived from this software without specific
prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NOTICE.html

VERIFICATION.txt

EventStoreDB is owned and created by Event Store

To verify the binaries:

* Navigate to the `eventstore` repository in Cloudsmith: https://cloudsmith.io/~eventstore/repos/eventstore
* Locate and download the nuget package for the released version. For instance:
    `https://packages.eventstore.com/public/eventstore/nuget/eventstoredb-ee/24.10.0/eventstoredb-ee.24.10.0.nupkg`
* Unpack the nuget package.
* Verify the checksum of the zipped package (e.g. `eventstoredb-24.10.0-ee-windows.x64.zip`) against the checksum shown on the package page of the community repository.

Virus Scan Results

System.CommandLine.dll (66740898f7df) - ## / 75
Humanizer.dll (d6853075547d) - ## / 73
msvcp140.dll (44a5af24f8d5) - ## / 71
vcruntime140.dll (1729421a2258) - ## / 72
Microsoft.Bcl.AsyncInterfaces.dll (5705d245072d) - ## / 70
Newtonsoft.Json.dll (22c649f75fce) - ## / 67
System.Linq.Async.dll (149757a4113a) - ## / 72
System.Configuration.ConfigurationManager.dll (89d52b4a10b1) - ## / 73
System.Security.Cryptography.ProtectedData.dll (5e04d6cff3b6) - ## / 73
System.ComponentModel.Composition.dll (82260fef3a01) - ## / 75
System.Diagnostics.PerformanceCounter.dll (fb93811a325a) - ## / 73
Microsoft.DiaSymReader.Native.amd64.dll (7f8dcf37d9d6) - ## / 72
msquic.dll (2d67e87859ec) - ## / 73
Microsoft.Extensions.Configuration.Binder.dll (beac12f7bba4) - ## / 75
SQLitePCLRaw.core.dll (c33995427edd) - ## / 73
Microsoft.Extensions.Configuration.FileExtensions.dll (acf5896d0f34) - ## / 72
Microsoft.Extensions.Configuration.Json.dll (15e1262880f2) - ## / 72
eventstoredb-24.10.0-ee-windows.x64.zip (d8b1cc8de44c) - ## / 52
eventstoredb-ee.24.10.0.nupkg (b3bd210c5420) - ## / 64
Acornima.dll (c8eff561bc29) - ## / 74
aspnetcorev2_inprocess.dll (2247c2e9d490) - ## / 73
clretwrc.dll (dd65f2279cce) - ## / 73
clrgc.dll (9b254c85d28e) - ## / 73
clrjit.dll (0dfe34be7814) - ## / 72
coreclr.dll (b4375494bb10) - ## / 72
createdump.exe (b24fd57ec869) - ## / 72
Dia2Lib.dll (6c4cac68010f) - ## / 74
DotNext.dll (131f3ac1c886) - ## / 72
DotNext.IO.dll (5ce59d50e441) - ## / 73
DotNext.Threading.dll (0fb20d52763b) - ## / 72
DotNext.Unsafe.dll (7349c52a35a9) - ## / 73
EventStore.BufferManagement.dll (46f892794c20) - ## / 73
EventStore.Client.dll (2f8bd957f4ea) - ## / 73
EventStore.Client.Streams.dll (cc30a60f23f4) - ## / 72
EventStore.ClientAPI.dll (37bb79cb82ee) - ## / 70
EventStore.ClusterNode.dll (22beefa0ecec) - ## / 73
EventStore.ClusterNode.exe (1a1c35cc98d9) - ## / 73
EventStore.ClusterNode.Web.dll (7ca41a06b455) - ## / 73
EventStore.Common.dll (c3a3eb8673ee) - ## / 73
EventStore.Core.dll (974969039603) - ## / 72
EventStore.Licensing.dll (2bfe42e2d78e) - ## / 73
EventStore.LogCommon.dll (6de37949bee0) - ## / 73
EventStore.LogV3.dll (d38b3f30f654) - ## / 73
EventStore.Native.dll (9539a0fb659b) - ## / 72
EventStore.NETCore.Compatibility.dll (4676151b6514) - ## / 73
EventStore.PluginHosting.dll (01ea23e68ef1) - ## / 73
EventStore.Plugins.dll (73704fc5d913) - ## / 72
EventStore.Projections.Core.dll (003417737f6b) - ## / 73
EventStore.SystemRuntime.dll (c57d6d79219d) - ## / 73
EventStore.TestClient.dll (2cb9edab88fc) - ## / 73
EventStore.TestClient.exe (90006850ddb3) - ## / 72
EventStore.Transport.Http.dll (5a282632bbd7) - ## / 73
EventStore.Transport.Tcp.dll (baf7789a1949) - ## / 73
e_sqlite3.dll (dccbabb2bc7e) - ## / 73
FASTER.core.dll (2dd9c11fbd78) - ## / 75
Google.Protobuf.dll (dd0de3d02732) - ## / 73
Grpc.AspNetCore.Server.ClientFactory.dll (6cf33037808d) - ## / 70
Grpc.AspNetCore.Server.dll (6748901c27df) - ## / 72
Grpc.Core.Api.dll (b347d4007569) - ## / 75
Grpc.Net.Client.dll (c75e7e15a892) - ## / 75
Grpc.Net.ClientFactory.dll (a94498074bdc) - ## / 71
Grpc.Net.Common.dll (2e820bc03804) - ## / 75
hostfxr.dll (130a3656b07a) - ## / 73
hostpolicy.dll (65d61078b6b9) - ## / 73
JetBrains.Annotations.dll (5f2b1475a7d8) - ## / 73
Jint.dll (cf5da4795287) - ## / 72
libcrypto-3-x64.dll (a6f51858b8f4) - ## / 75
libcurl.dll (04de2857dffd) - ## / 74
libMonoPosixHelper.dll (b16f77c155a3) - ## / 73
librdkafka.dll (a0735e29fed5) - ## / 74
librdkafkacpp.dll (613d8ef1d38e) - ## / 74
libssl-3-x64.dll (7836b7acc290) - ## / 74
Microsoft.AspNetCore.Antiforgery.dll (0eb9c2b80c3f) - ## / 70
Microsoft.AspNetCore.Authentication.Abstractions.dll (0e14cdff066f) - ## / 73
Microsoft.AspNetCore.Authentication.BearerToken.dll (f24174bce7f1) - ## / 73
Microsoft.AspNetCore.Authentication.Cookies.dll (4f4b0a27c85b) - ## / 73
Microsoft.AspNetCore.Authentication.Core.dll (2423d2b873e5) - ## / 73
Microsoft.AspNetCore.Authentication.dll (fdf46239e896) - ## / 73
Microsoft.AspNetCore.Authentication.OAuth.dll (076e19cbed4a) - ## / 73
Microsoft.AspNetCore.Authorization.dll (02701a7a9ae6) - ## / 73
Microsoft.AspNetCore.Authorization.Policy.dll (0e866657ab89) - ## / 65
Microsoft.AspNetCore.Components.Authorization.dll (9c0e0d57ae6a) - ## / 73
Microsoft.AspNetCore.Components.dll (bb2d58f039da) - ## / 72
Microsoft.AspNetCore.Components.Endpoints.dll (7c8502b3c240) - ## / 70
Microsoft.AspNetCore.Components.Forms.dll (44ce3ef708d4) - ## / 73
Microsoft.AspNetCore.Components.Server.dll (9b4c14e2b82d) - ## / 73
Microsoft.AspNetCore.Components.Web.dll (eb95750e33bb) - ## / 68
Microsoft.AspNetCore.Connections.Abstractions.dll (9efbe464ac12) - ## / 73
Microsoft.AspNetCore.CookiePolicy.dll (26835444c40a) - ## / 72
Microsoft.AspNetCore.Cors.dll (0a618da3df59) - ## / 73
Microsoft.AspNetCore.Cryptography.Internal.dll (935f39dc3020) - ## / 73
Microsoft.AspNetCore.Cryptography.KeyDerivation.dll (7205696eab08) - ## / 73
Microsoft.AspNetCore.DataProtection.Abstractions.dll (523b7bc65227) - ## / 73
Microsoft.AspNetCore.DataProtection.dll (e1f73de92c98) - ## / 73
Microsoft.AspNetCore.DataProtection.Extensions.dll (5e9c6bc48caf) - ## / 73
Microsoft.AspNetCore.Diagnostics.Abstractions.dll (e9272db02894) - ## / 73
Microsoft.AspNetCore.Diagnostics.dll (941cae592a25) - ## / 73
Microsoft.AspNetCore.Diagnostics.HealthChecks.dll (6882cdc67769) - ## / 73
Microsoft.AspNetCore.dll (7463fa9bfadd) - ## / 73
Microsoft.AspNetCore.HostFiltering.dll (cbfb422cb51c) - ## / 73
Microsoft.AspNetCore.Hosting.Abstractions.dll (6e0f63078670) - ## / 73
Microsoft.AspNetCore.Hosting.dll (e6b5e76e59c7) - ## / 73
Microsoft.AspNetCore.Hosting.Server.Abstractions.dll (1e81b532b169) - ## / 73
Microsoft.AspNetCore.Html.Abstractions.dll (70778d6d9984) - ## / 70
Microsoft.AspNetCore.Http.Abstractions.dll (31bc5df86d06) - ## / 73
Microsoft.AspNetCore.Http.Connections.Common.dll (d0d7578918db) - ## / 72
Microsoft.AspNetCore.Http.Connections.dll (9ac203277a32) - ## / 72
Microsoft.AspNetCore.Http.dll (1be49a6f42a4) - ## / 73
Microsoft.AspNetCore.Http.Extensions.dll (08affdb7892c) - ## / 73
Microsoft.AspNetCore.Http.Features.dll (3dd98c30965c) - ## / 73
Microsoft.AspNetCore.Http.Results.dll (0c8a85f72c56) - ## / 73
Microsoft.AspNetCore.HttpLogging.dll (c95ee5f95719) - ## / 68
Microsoft.AspNetCore.HttpOverrides.dll (5a3bc07b7e11) - ## / 70
Microsoft.AspNetCore.HttpsPolicy.dll (c0cc9050da4d) - ## / 73
Microsoft.AspNetCore.Identity.dll (dbb55fbb186e) - ## / 73
Microsoft.AspNetCore.Localization.dll (7d0ad5b6d6aa) - ## / 73
Microsoft.AspNetCore.Localization.Routing.dll (08f5e6b393e3) - ## / 73
Microsoft.AspNetCore.Metadata.dll (919173311c00) - ## / 65
Microsoft.AspNetCore.Mvc.Abstractions.dll (f9d3ecfacb33) - ## / 73
Microsoft.AspNetCore.Mvc.ApiExplorer.dll (cabe43494e13) - ## / 71
Microsoft.AspNetCore.Mvc.Core.dll (eda45644965b) - ## / 73
Microsoft.AspNetCore.Mvc.Cors.dll (f47156b7cb20) - ## / 73
Microsoft.AspNetCore.Mvc.DataAnnotations.dll (fc74cb7d0e3c) - ## / 70
Microsoft.AspNetCore.Mvc.dll (0dee46f1b516) - ## / 68
Microsoft.AspNetCore.Mvc.Formatters.Json.dll (13cf4f794a94) - ## / 68
Microsoft.AspNetCore.Mvc.Formatters.Xml.dll (8d9e85706f6b) - ## / 73
Microsoft.AspNetCore.Mvc.Localization.dll (f42a70e6f857) - ## / 73
Microsoft.AspNetCore.Mvc.Razor.dll (c7a7a357b4bc) - ## / 73
Microsoft.AspNetCore.Mvc.RazorPages.dll (8dc43d9c7bdd) - ## / 73
Microsoft.AspNetCore.Mvc.TagHelpers.dll (f03a764f9949) - ## / 70
Microsoft.AspNetCore.Mvc.ViewFeatures.dll (73e51371fb4f) - ## / 72
Microsoft.AspNetCore.OutputCaching.dll (11e6f2c1222b) - ## / 73
Microsoft.AspNetCore.RateLimiting.dll (fef78b809993) - ## / 73
Microsoft.AspNetCore.Razor.dll (207c4bebe3d7) - ## / 73
Microsoft.AspNetCore.Razor.Runtime.dll (58d8b38dd8e0) - ## / 73
Microsoft.AspNetCore.RequestDecompression.dll (c77e1460584d) - ## / 73
Microsoft.AspNetCore.ResponseCaching.Abstractions.dll (e1da039f4e67) - ## / 73
Microsoft.AspNetCore.ResponseCaching.dll (6f5d2a14df10) - ## / 73
Microsoft.AspNetCore.ResponseCompression.dll (1c88774e587d) - ## / 73
Microsoft.AspNetCore.Rewrite.dll (e5009617dc26) - ## / 73
Microsoft.AspNetCore.Routing.Abstractions.dll (ec9d99761e3d) - ## / 73
Microsoft.AspNetCore.Routing.dll (c35aa5301da1) - ## / 73
Microsoft.AspNetCore.Server.HttpSys.dll (96587bcab61e) - ## / 73
Microsoft.AspNetCore.Server.IIS.dll (3387432f4a7d) - ## / 73
Microsoft.AspNetCore.Server.IISIntegration.dll (8e430f5ae37c) - ## / 73
Microsoft.AspNetCore.Server.Kestrel.Core.dll (40af4fe75ab7) - ## / 73
Microsoft.AspNetCore.Server.Kestrel.dll (300cbd7833e1) - ## / 73
Microsoft.AspNetCore.Server.Kestrel.Transport.NamedPipes.dll (bced529c3595) - ## / 73
Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.dll (57c929859a74) - ## / 73
Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.dll (67ebfcf25bb9) - ## / 73
Microsoft.AspNetCore.Session.dll (9938cffd83e3) - ## / 70
Microsoft.AspNetCore.SignalR.Common.dll (5d96cfb6426c) - ## / 73
Microsoft.AspNetCore.SignalR.Core.dll (234d44a05e74) - ## / 73
Microsoft.AspNetCore.SignalR.dll (388eedbb6738) - ## / 73
Microsoft.AspNetCore.SignalR.Protocols.Json.dll (112ba0c398fa) - ## / 72
Microsoft.AspNetCore.StaticFiles.dll (0aae9c4f09da) - ## / 73
Microsoft.AspNetCore.WebSockets.dll (582fc8165f8f) - ## / 73
Microsoft.AspNetCore.WebUtilities.dll (554a6e1aa871) - ## / 73
Microsoft.CSharp.dll (099bc112dc64) - ## / 72
Microsoft.Data.Sqlite.dll (29981956955d) - ## / 70
Microsoft.Diagnostics.FastSerialization.dll (3652e4db69f5) - ## / 71
Microsoft.Diagnostics.NETCore.Client.dll (8df3f1d366e4) - ## / 71
Microsoft.Diagnostics.Tracing.TraceEvent.dll (d48ae2c17530) - ## / 56
Microsoft.Extensions.Caching.Abstractions.dll (52aad8c909c5) - ## / 73
Microsoft.Extensions.Caching.Memory.dll (7d2fc3ef11db) - ## / 73
Microsoft.Extensions.Configuration.Abstractions.dll (ef7df0d6667b) - ## / 73
Microsoft.Extensions.Configuration.Binder.dll (e3de94d75203) - ## / 72
Microsoft.Extensions.Configuration.CommandLine.dll (b60aed101639) - ## / 65
Microsoft.Extensions.Configuration.dll (571a9c2a7bac) - ## / 72
Microsoft.Extensions.Configuration.EnvironmentVariables.dll (53f53e5e1253) - ## / 73
Microsoft.Extensions.Configuration.FileExtensions.dll (091da842465b) - ## / 73
Microsoft.Extensions.Configuration.Ini.dll (2cba2987c177) - ## / 73
Microsoft.Extensions.Configuration.Json.dll (da41acad141e) - ## / 73
Microsoft.Extensions.Configuration.KeyPerFile.dll (eb4c0fb705dd) - ## / 73
Microsoft.Extensions.Configuration.UserSecrets.dll (35379a80362f) - ## / 73
Microsoft.Extensions.Configuration.Xml.dll (9e5e256f3290) - ## / 70
Microsoft.Extensions.DependencyInjection.Abstractions.dll (86b03ea4a0d8) - ## / 73
Microsoft.Extensions.DependencyInjection.dll (3dd4ea889bd3) - ## / 73
Microsoft.Extensions.DependencyModel.dll (fa0201d4731d) - ## / 73
Microsoft.Extensions.Diagnostics.Abstractions.dll (9586d9cd55a6) - ## / 73
Microsoft.Extensions.Diagnostics.dll (0d084601dda5) - ## / 73
Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions.dll (3c97fbbfb429) - ## / 72
Microsoft.Extensions.Diagnostics.HealthChecks.dll (2f11cf80febf) - ## / 73
Microsoft.Extensions.Features.dll (47cef47a3f72) - ## / 73
Microsoft.Extensions.FileProviders.Abstractions.dll (94e4d25a94e7) - ## / 73
Microsoft.Extensions.FileProviders.Composite.dll (8ee580cdb838) - ## / 73
Microsoft.Extensions.FileProviders.Embedded.dll (13ed61fa0947) - ## / 72
Microsoft.Extensions.FileProviders.Physical.dll (fc289ff18d95) - ## / 73
Microsoft.Extensions.FileSystemGlobbing.dll (e9a5d4b5ac69) - ## / 73
Microsoft.Extensions.Hosting.Abstractions.dll (fe69379c37f0) - ## / 73
Microsoft.Extensions.Hosting.dll (8f3748593381) - ## / 73
Microsoft.Extensions.Http.dll (1169d2ef4db1) - ## / 73
Microsoft.Extensions.Identity.Core.dll (2206444d03f4) - ## / 73
Microsoft.Extensions.Identity.Stores.dll (e363a5a6e6bd) - ## / 73
Microsoft.Extensions.Localization.Abstractions.dll (de63e438e948) - ## / 73
Microsoft.Extensions.Localization.dll (1722b6197926) - ## / 73
Microsoft.Extensions.Logging.Abstractions.dll (92cf9ae967bc) - ## / 73
Microsoft.Extensions.Logging.Configuration.dll (ffcc667806e3) - ## / 73
Microsoft.Extensions.Logging.Console.dll (1b4eaf137bad) - ## / 73
Microsoft.Extensions.Logging.Debug.dll (e5052306cebb) - ## / 73
Microsoft.Extensions.Logging.dll (77fa3de46cc5) - ## / 72
Microsoft.Extensions.Logging.EventLog.dll (4de78774642f) - ## / 73
Microsoft.Extensions.Logging.EventSource.dll (d3db4b7b8cb2) - ## / 73
Microsoft.Extensions.Logging.TraceSource.dll (fd241dcc9f5b) - ## / 73
Microsoft.Extensions.ObjectPool.dll (4600ff58171a) - ## / 70
Microsoft.Extensions.Options.ConfigurationExtensions.dll (69a60c99ba84) - ## / 73
Microsoft.Extensions.Options.DataAnnotations.dll (b534d7c65229) - ## / 73
Microsoft.Extensions.Options.dll (94b24e1cd3d2) - ## / 73
Microsoft.Extensions.Primitives.dll (045af60cce67) - ## / 73
Microsoft.Extensions.WebEncoders.dll (4786bf95b42c) - ## / 73
Microsoft.IdentityModel.Abstractions.dll (55a43cdc091d) - ## / 74
Microsoft.IdentityModel.JsonWebTokens.dll (cb297e8a440b) - ## / 74
Microsoft.IdentityModel.Logging.dll (ecbfaf9ef2f0) - ## / 75
Microsoft.IdentityModel.Tokens.dll (bb75d1edc488) - ## / 75
Microsoft.JSInterop.dll (8a0159d89bca) - ## / 73
Microsoft.Net.Http.Headers.dll (37be2e1006b0) - ## / 73
Microsoft.VisualBasic.Core.dll (816de66126c5) - ## / 72
Microsoft.VisualBasic.dll (bd36d4fd23d7) - ## / 73
Microsoft.Win32.Primitives.dll (150ce7473f17) - ## / 71
Microsoft.Win32.Registry.dll (19eab1189558) - ## / 72
Mono.Posix.NETStandard.dll (be0215d90462) - ## / 75
MonoPosixHelper.dll (a57141b26d6e) - ## / 73
mscordaccore.dll (6c52462719dc) - ## / 73
mscordbi.dll (a91540e748cb) - ## / 73
mscorlib.dll (2f8e23c3566b) - ## / 73
mscorrc.dll (7d2f7896b526) - ## / 72
NetEscapades.Configuration.Yaml.dll (c7f2c6408e2b) - ## / 70
netstandard.dll (f56c741cc18d) - ## / 73
OpenTelemetry.Api.dll (601a69f6a24d) - ## / 65
OpenTelemetry.dll (b52f644b7274) - ## / 65
OpenTelemetry.Exporter.Prometheus.AspNetCore.dll (d400e09961ff) - ## / 66
OpenTelemetry.Extensions.DependencyInjection.dll (31f214ae4f56) - ## / 70
OpenTelemetry.Extensions.Hosting.dll (3b5b1ad74272) - ## / 66
protobuf-net.dll (748eab8a89cb) - ## / 67
Quickenshtein.dll (5126a62e6e38) - ## / 72
RestSharp.dll (b3cefa0b7623) - ## / 73
Serilog.dll (521306297946) - ## / 74
Serilog.Enrichers.Process.dll (78ea61f1b96e) - ## / 75
Serilog.Enrichers.Thread.dll (74b88ad495b8) - ## / 75
Serilog.Expressions.dll (e3fc0c1c14ab) - ## / 67
Serilog.Extensions.Logging.dll (a0b6c860fa5b) - ## / 72
Serilog.Settings.Configuration.dll (de2346b3df0a) - ## / 74
Serilog.Sinks.Async.dll (22cc5ff74edc) - ## / 73
Serilog.Sinks.Console.dll (cd84c110a96a) - ## / 73
Serilog.Sinks.File.dll (fe02a7c70b06) - ## / 72
SharpDotYaml.Extensions.Configuration.dll (0f117fa24d8a) - ## / 75
SQLitePCLRaw.batteries_v2.dll (e2709fda3ee4) - ## / 73
SQLitePCLRaw.provider.e_sqlite3.dll (66a5ea09aa31) - ## / 71
System.AppContext.dll (1ee0c49348e8) - ## / 73
System.Buffers.dll (49bd03ff5ef0) - ## / 72
System.Collections.Concurrent.dll (4cc75a63fed0) - ## / 72
System.Collections.dll (5b20181ee4e1) - ## / 73
System.Collections.Immutable.dll (6446e921cf1d) - ## / 73
System.Collections.NonGeneric.dll (891a7b6baa99) - ## / 73
System.Collections.Specialized.dll (b2eabd2cc992) - ## / 71
System.CommandLine.DragonFruit.dll (085d81f6e1a4) - ## / 75
System.CommandLine.Rendering.dll (e539944b0431) - ## / 73
System.ComponentModel.Annotations.dll (7abbb89a3b17) - ## / 73
System.ComponentModel.DataAnnotations.dll (e49b3f50fdb6) - ## / 73
System.ComponentModel.dll (0bf9e3e6c832) - ## / 73
System.ComponentModel.EventBasedAsync.dll (6c2ba6173203) - ## / 73
System.ComponentModel.Primitives.dll (304635dbc025) - ## / 73
System.ComponentModel.TypeConverter.dll (cd7e2ef84253) - ## / 73
System.Configuration.dll (19c65ddfd1c4) - ## / 72
System.Console.dll (8469deb8c7d5) - ## / 73
System.Core.dll (cc23f980e20f) - ## / 73
System.Data.Common.dll (85614a082fdb) - ## / 72
System.Data.DataSetExtensions.dll (55e5bd120160) - ## / 73
System.Data.dll (04c204b1fc3b) - ## / 73
System.Diagnostics.Contracts.dll (f8179ef7837f) - ## / 73
System.Diagnostics.Debug.dll (f587e4d5f434) - ## / 73
System.Diagnostics.DiagnosticSource.dll (9444173233a1) - ## / 73
System.Diagnostics.EventLog.dll (35032a03596e) - ## / 73
System.Diagnostics.EventLog.Messages.dll (8b196ac3d360) - ## / 73
System.Diagnostics.FileVersionInfo.dll (ab5638a08516) - ## / 73
System.Diagnostics.Process.dll (7bbca593ed7f) - ## / 67
System.Diagnostics.StackTrace.dll (2911fcad2139) - ## / 71
System.Diagnostics.TextWriterTraceListener.dll (1a1cb8d5807b) - ## / 73
System.Diagnostics.Tools.dll (383907734cd3) - ## / 73
System.Diagnostics.TraceSource.dll (cc685536eb20) - ## / 64
System.Diagnostics.Tracing.dll (07990d092b82) - ## / 70
System.dll (de72057e9a2e) - ## / 60
System.Drawing.dll (4ef5ce2dafc6) - ## / 73
System.Drawing.Primitives.dll (fa7d94825ec7) - ## / 73
System.Dynamic.Runtime.dll (9e24a4f92350) - ## / 73
System.Formats.Asn1.dll (689c8742ba53) - ## / 72
System.Formats.Tar.dll (4aaa042da8cc) - ## / 73
System.Globalization.Calendars.dll (c016ff9595bf) - ## / 73
System.Globalization.dll (b5809b999638) - ## / 73
System.Globalization.Extensions.dll (07c60ef102aa) - ## / 72
System.Interactive.Async.dll (caa6929aaecb) - ## / 73
System.IO.Compression.Brotli.dll (2172bdd60dde) - ## / 73
System.IO.Compression.dll (e595732c0655) - ## / 73
System.IO.Compression.FileSystem.dll (1481a72e898d) - ## / 73
System.IO.Compression.Native.dll (5146291e6ab9) - ## / 72
System.IO.Compression.ZipFile.dll (7ab974dc21ba) - ## / 73
System.IO.dll (ffc7d4206c7b) - ## / 73
System.IO.FileSystem.AccessControl.dll (3053ab194b17) - ## / 64
System.IO.FileSystem.dll (4a61b376b6e7) - ## / 73
System.IO.FileSystem.DriveInfo.dll (d7bf8354d118) - ## / 72
System.IO.FileSystem.Primitives.dll (7c2aef2bd75e) - ## / 72
System.IO.FileSystem.Watcher.dll (3b6bdfb5bad1) - ## / 73
System.IO.Hashing.dll (53726755857b) - ## / 73
System.IO.IsolatedStorage.dll (bc9eff07ba9b) - ## / 73
System.IO.MemoryMappedFiles.dll (c4ce83776faf) - ## / 73
System.IO.Pipelines.dll (bf1cf3f2e968) - ## / 73
System.IO.Pipes.AccessControl.dll (357478614e28) - ## / 73
System.IO.Pipes.dll (1972a42c7b90) - ## / 73
System.IO.UnmanagedMemoryStream.dll (5b614d49bba3) - ## / 73
System.Linq.dll (a2fb9dd80418) - ## / 72
System.Linq.Expressions.dll (f961c3396aad) - ## / 73
System.Linq.Parallel.dll (7004cf19931e) - ## / 73
System.Linq.Queryable.dll (7efda8ea3adc) - ## / 73
System.Memory.dll (536310fad46e) - ## / 71
System.Net.dll (18a45c63385c) - ## / 73
System.Net.Http.dll (d88a1e49ec7f) - ## / 73
System.Net.Http.Json.dll (aedf0405e533) - ## / 73
System.Net.HttpListener.dll (41f81f076d63) - ## / 73
System.Net.Mail.dll (e3efe9f18525) - ## / 71
System.Net.NameResolution.dll (67d6ce9d3592) - ## / 72
System.Net.NetworkInformation.dll (d3c0790e5354) - ## / 73
System.Net.Ping.dll (13428704a113) - ## / 71
System.Net.Primitives.dll (93fa4ad1590d) - ## / 73
System.Net.Quic.dll (24674d754f8d) - ## / 73
System.Net.Requests.dll (2af7c808f269) - ## / 59
System.Net.Security.dll (f8d695445499) - ## / 73
System.Net.ServicePoint.dll (613b5dc25c72) - ## / 72
System.Net.Sockets.dll (928cb7634629) - ## / 73
System.Net.WebClient.dll (e92ba4fcbe48) - ## / 73
System.Net.WebHeaderCollection.dll (7e1855c99655) - ## / 73
System.Net.WebProxy.dll (b28fa5fce149) - ## / 73
System.Net.WebSockets.Client.dll (5af953eee1e6) - ## / 73
System.Net.WebSockets.dll (5418618458aa) - ## / 73
System.Numerics.dll (8ceca85d001c) - ## / 73
System.Numerics.Vectors.dll (d15a0768577c) - ## / 72
System.ObjectModel.dll (447e24f4bfab) - ## / 73
System.Private.CoreLib.dll (4cd6810b4ebe) - ## / 71
System.Private.DataContractSerialization.dll (96c38be90900) - ## / 67
System.Private.Uri.dll (dc01ed420ef4) - ## / 73
System.Private.Xml.dll (79cdaefc2213) - ## / 73
System.Private.Xml.Linq.dll (13602313fc8b) - ## / 73
System.Reactive.dll (626b01d9a0a1) - ## / 73
System.Reflection.DispatchProxy.dll (f625aae4f7a8) - ## / 73
System.Reflection.dll (acd8f3ea0b14) - ## / 73
System.Reflection.Emit.dll (5be721dd3feb) - ## / 73
System.Reflection.Emit.ILGeneration.dll (7c85f57b009b) - ## / 72
System.Reflection.Emit.Lightweight.dll (9356d1216420) - ## / 73
System.Reflection.Extensions.dll (f006c1df7449) - ## / 73
System.Reflection.Metadata.dll (a82da76c39dd) - ## / 72
System.Reflection.Primitives.dll (081035e2019f) - ## / 67
System.Reflection.TypeExtensions.dll (1c5ac607683f) - ## / 73
System.Resources.Reader.dll (4ee54b35de61) - ## / 71
System.Resources.ResourceManager.dll (78ea4958bba5) - ## / 73
System.Resources.Writer.dll (9175ef26f743) - ## / 73
System.Runtime.CompilerServices.Unsafe.dll (2dc6d8d20af5) - ## / 73
System.Runtime.CompilerServices.VisualC.dll (2cf2328b2bb6) - ## / 71
System.Runtime.dll (9c506c9347f8) - ## / 73
System.Runtime.Extensions.dll (c31f0812b878) - ## / 73
System.Runtime.Handles.dll (ff10134a6ab7) - ## / 73
System.Runtime.InteropServices.dll (127ea3f2ff47) - ## / 73
System.Runtime.InteropServices.JavaScript.dll (b5415b6be10c) - ## / 73
System.Runtime.InteropServices.RuntimeInformation.dll (357797fea3e2) - ## / 73
System.Runtime.Intrinsics.dll (3a18c5b41b72) - ## / 72
System.Runtime.Loader.dll (f106df84a047) - ## / 73
System.Runtime.Numerics.dll (55d0e21e8ad1) - ## / 59
System.Runtime.Serialization.dll (06cd0bd2011f) - ## / 59
System.Runtime.Serialization.Formatters.dll (748cce10a02b) - ## / 73
System.Runtime.Serialization.Json.dll (53bde641865f) - ## / 71
System.Runtime.Serialization.Primitives.dll (1439d12a15b1) - ## / 73
System.Runtime.Serialization.Xml.dll (d37e6a8f6b38) - ## / 73
System.Security.AccessControl.dll (de77b6a860b6) - ## / 72
System.Security.Claims.dll (9aedeb23632f) - ## / 73
System.Security.Cryptography.Algorithms.dll (a28c5ad8cfc5) - ## / 72
System.Security.Cryptography.Cng.dll (a589ac8a9e90) - ## / 72
System.Security.Cryptography.Csp.dll (5da38d4a9eb6) - ## / 71
System.Security.Cryptography.dll (028606c9c16a) - ## / 72
System.Security.Cryptography.Encoding.dll (aa82b36af87d) - ## / 72
System.Security.Cryptography.OpenSsl.dll (f644b4fa91d1) - ## / 64
System.Security.Cryptography.Pkcs.dll (a2b8c5065bdb) - ## / 73
System.Security.Cryptography.Primitives.dll (13bc71596817) - ## / 72
System.Security.Cryptography.X509Certificates.dll (5826e377c017) - ## / 72
System.Security.Cryptography.Xml.dll (7e296038097e) - ## / 72
System.Security.dll (c0f486c4fc81) - ## / 73
System.Security.Principal.dll (902d836b8cb0) - ## / 73
System.Security.Principal.Windows.dll (59815feab7b4) - ## / 71
System.Security.SecureString.dll (1af90d82a617) - ## / 73
System.ServiceModel.Http.dll (f202e323c796) - ## / 67
System.ServiceModel.Primitives.dll (63c701108c72) - ## / 72
System.ServiceModel.Web.dll (3d08eb5338c0) - ## / 73
System.ServiceProcess.dll (634a5d94940a) - ## / 73
System.Text.Encoding.CodePages.dll (85f3296c927e) - ## / 73
System.Text.Encoding.dll (5f1faa881876) - ## / 73
System.Text.Encoding.Extensions.dll (a875d0785cae) - ## / 73
System.Text.Encodings.Web.dll (cf456fa426be) - ## / 71
System.Text.Json.dll (93b1e1e67704) - ## / 73
System.Text.RegularExpressions.dll (0fecfac9bdd4) - ## / 73
System.Threading.Channels.dll (985df4c7ac42) - ## / 72
System.Threading.dll (15cc9db291b8) - ## / 73
System.Threading.Overlapped.dll (00ee20495cd0) - ## / 73
System.Threading.RateLimiting.dll (e52a41e669fe) - ## / 73
System.Threading.Tasks.Dataflow.dll (fb97f3acd266) - ## / 72
System.Threading.Tasks.dll (71f1b7847ed8) - ## / 73
System.Threading.Tasks.Extensions.dll (b1dc1408c743) - ## / 71
System.Threading.Tasks.Parallel.dll (43d450bb7b0d) - ## / 73
System.Threading.Thread.dll (ecbe1cde0de9) - ## / 60
System.Threading.ThreadPool.dll (5913e28b4b0e) - ## / 72
System.Threading.Timer.dll (4a3352e5c488) - ## / 73
System.Transactions.dll (033ad774b53a) - ## / 73
System.Transactions.Local.dll (981215f0ee08) - ## / 73
System.ValueTuple.dll (4b3c5f41f52f) - ## / 72
System.Web.dll (9351d54c7407) - ## / 73
System.Web.HttpUtility.dll (f1a590e321d8) - ## / 67
System.Windows.dll (60e61212b441) - ## / 73
System.Xml.dll (c55afca244ea) - ## / 72
System.Xml.Linq.dll (79d0149a2469) - ## / 73
System.Xml.ReaderWriter.dll (0ebf6e07ac4c) - ## / 73
System.Xml.Serialization.dll (c9c61183df3f) - ## / 64
System.Xml.XDocument.dll (5bf169370863) - ## / 73
System.Xml.XmlDocument.dll (bae0097f29c7) - ## / 67
System.Xml.XmlSerializer.dll (9399f32559dc) - ## / 72
System.Xml.XPath.dll (6af1a8c435ef) - ## / 73
System.Xml.XPath.XDocument.dll (865c8934588f) - ## / 60
TraceReloggerLib.dll (6830c0f1d3f3) - ## / 59
WindowsBase.dll (54123fc5b700) - ## / 73
YamlDotNet.dll (5a7f117d2ef5) - ## / 72
zlib1.dll (411cbd82a6a4) - ## / 73
zstd.dll (265ebf766ca8) - ## / 71
KernelTraceControl.dll (98de2f1de4fb) - ## / 74
msdia140.dll (a984a45afedf) - ## / 67
System.CommandLine.resources.dll (1b59c63dd853) - ## / 72
System.ServiceModel.Http.resources.dll (4cfe1399e19f) - ## / 69
System.ServiceModel.Primitives.resources.dll (fefc46ca75e3) - ## / 69
System.CommandLine.resources.dll (ea64ff09c5d7) - ## / 74
System.ServiceModel.Http.resources.dll (b14c0f6f6090) - ## / 69
System.ServiceModel.Primitives.resources.dll (2416155129e2) - ## / 69
System.CommandLine.resources.dll (155eb865b536) - ## / 74
System.ServiceModel.Http.resources.dll (d8303bf3854d) - ## / 69
System.ServiceModel.Primitives.resources.dll (0578488ac8f0) - ## / 69
System.CommandLine.resources.dll (97035ec2904b) - ## / 73
System.ServiceModel.Http.resources.dll (df57e80149d2) - ## / 69
System.ServiceModel.Primitives.resources.dll (deb8f4b0506b) - ## / 69
System.CommandLine.resources.dll (8fea3a65aa57) - ## / 73
System.ServiceModel.Http.resources.dll (04555d7c0a06) - ## / 69
System.ServiceModel.Primitives.resources.dll (47d32f965a59) - ## / 69
System.CommandLine.resources.dll (36b0caefff39) - ## / 73
System.ServiceModel.Http.resources.dll (0b076289939f) - ## / 68
System.ServiceModel.Primitives.resources.dll (b997f86bc901) - ## / 69
System.CommandLine.resources.dll (7cb2aa1d1422) - ## / 72
System.ServiceModel.Http.resources.dll (555755684f00) - ## / 69
System.ServiceModel.Primitives.resources.dll (3a966f10481b) - ## / 69
System.CommandLine.resources.dll (41d97925f99b) - ## / 74
System.ServiceModel.Http.resources.dll (bf7605ffb687) - ## / 69
System.ServiceModel.Primitives.resources.dll (c41f26a75f4f) - ## / 69
System.CommandLine.resources.dll (a6f1069a80fc) - ## / 72
System.ServiceModel.Http.resources.dll (9f301d7c0016) - ## / 69
System.ServiceModel.Primitives.resources.dll (a5503b7db3aa) - ## / 68
System.CommandLine.resources.dll (6f0e98f7ed86) - ## / 74
System.ServiceModel.Http.resources.dll (15ba7da2161c) - ## / 72
System.ServiceModel.Primitives.resources.dll (a37e8d18694d) - ## / 71
System.CommandLine.resources.dll (454be65124cd) - ## / 74
System.ServiceModel.Http.resources.dll (d6d398578cfc) - ## / 69
System.ServiceModel.Primitives.resources.dll (f15688ec76ba) - ## / 69
System.CommandLine.resources.dll (cc6224ef1f48) - ## / 74
System.ServiceModel.Http.resources.dll (d2b8f7ab808b) - ## / 69
System.ServiceModel.Primitives.resources.dll (f46341061677) - ## / 69
System.CommandLine.resources.dll (e844e9719620) - ## / 74
System.ServiceModel.Http.resources.dll (455a3f363781) - ## / 69
System.ServiceModel.Primitives.resources.dll (b1bc0f540fb4) - ## / 69
libcrypto-3.dll (c44f415592d4) - ## / 74
libcurl.dll (858637c49b43) - ## / 74
librdkafka.dll (f57276b7537e) - ## / 74
librdkafkacpp.dll (16469ac3c836) - ## / 72
libssl-3.dll (84623a3da0b4) - ## / 70
msvcp140.dll (5e78aaaf2096) - ## / 73
vcruntime140.dll (08de0ede013d) - ## / 73
zlib1.dll (8936bed727b9) - ## / 72
zstd.dll (ff8b977c468b) - ## / 74
EventStore.Auth.Ldaps.dll (1804a52dbd80) - ## / 73
Novell.Directory.Ldap.NETStandard.dll (85918b6f9e91) - ## / 74
Serilog.dll (f9aa9b349984) - ## / 72
EventStore.Auth.LegacyAuthorizationWithStreamAuthorizationDisabled.dll (5c50074e489b) - ## / 73
EventStore.Auth.OAuth.dll (046dce2ba6cb) - ## / 73
IdentityModel.dll (5fdb11082d6b) - ## / 69
LruCacheNet.dll (036a16dc1b49) - ## / 70
System.IdentityModel.Tokens.Jwt.dll (88f0e89fdf39) - ## / 72
EventStore.Auth.StreamPolicyPlugin.dll (cd4280575ebc) - ## / 72
EventStore.Auth.UserCertificates.dll (b77244a9f44b) - ## / 72
Microsoft.Extensions.DependencyModel.dll (b6406254657a) - ## / 66
Scrutor.dll (69e6a275558e) - ## / 73
EventStore.AutoScavenge.dll (89c820bc927a) - ## / 73
NCrontab.dll (2dfc5258a60c) - ## / 75
EventStore.POC.ConnectedSubsystemsPlugin.dll (79476dc153db) - ## / 70
EventStore.POC.IO.Core.dll (780e2db78181) - ## / 73
Avro.dll (3c7dc414c8b7) - ## / 71
Confluent.Kafka.dll (7280ac1b37ba) - ## / 73
Confluent.SchemaRegistry.dll (934f59da5b23) - ## / 73
Confluent.SchemaRegistry.Serdes.Avro.dll (1971d62b1b5e) - ## / 72
Confluent.SchemaRegistry.Serdes.Json.dll (ee618b08e2e7) - ## / 73
Confluent.SchemaRegistry.Serdes.Protobuf.dll (80236efd9765) - ## / 73
DnsClient.dll (a6aa942bf9f1) - ## / 75
EventStore.Client.dll (518d0cff5814) - ## / 73
EventStore.Client.Operations.dll (2c227f9a495e) - ## / 73
EventStore.Client.Streams.dll (4079074cfd1c) - ## / 73
EventStore.Connectors.EventStoreDB.dll (a57cd9b8f934) - ## / 70
EventStore.Connectors.Http.dll (c94b32a3792a) - ## / 72
EventStore.Connectors.Kafka.dll (dfcf4888cb7e) - ## / 72
EventStore.Connectors.MongoDB.dll (3de8129dd8b7) - ## / 73
EventStore.Connectors.RabbitMQ.dll (753cf1008ee1) - ## / 72
EventStore.Extensions.Connectors.Contracts.dll (6ba7fe8b53b4) - ## / 72
EventStore.Extensions.Connectors.dll (d4198ea674d9) - ## / 70
EventStore.Plugins.Connectors.dll (e6cec5674c65) - ## / 73
EventStore.Streaming.Core.dll (4350005f4fbb) - ## / 73
EventStore.Streaming.dll (fa68b347db33) - ## / 73
Eventuous.Application.dll (d5b6ca4d5640) - ## / 73
Eventuous.Diagnostics.dll (7e9bfb8d68ab) - ## / 73
Eventuous.Diagnostics.Logging.dll (3033cabb86c5) - ## / 73
Eventuous.Domain.dll (7a0b9edf13cf) - ## / 61
Eventuous.Extensions.AspNetCore.dll (5f3518c2f97e) - ## / 73
Eventuous.Extensions.DependencyInjection.dll (d9658b528327) - ## / 73
Eventuous.Persistence.dll (8cf8b107030e) - ## / 71
Eventuous.Serialization.dll (a7fd1fa58504) - ## / 70
Eventuous.Shared.dll (d1ab993f9117) - ## / 73
FluentValidation.DependencyInjectionExtensions.dll (50373c54e3ae) - ## / 67
FluentValidation.dll (736b60afdae2) - ## / 73
Google.Api.CommonProtos.dll (7a08e7346c52) - ## / 70
Grpc.Core.Api.dll (2b9e8b023dea) - ## / 73
Grpc.StatusProto.dll (3d7de3a5b126) - ## / 73
HashDepot.dll (47dd1b0607d1) - ## / 72
Json.More.dll (67fea7f0915e) - ## / 75
JsonCons.JsonPath.dll (464b02a00c3b) - ## / 70
JsonCons.Utilities.dll (e2da3c771b50) - ## / 71
JsonPath.Net.dll (e91a849089fe) - ## / 72
libcrypto-3-x64.dll (8410f2038651) - ## / 73
libcurl.dll (220b4158d653) - ## / 71
librdkafka.dll (e041e2a075a0) - ## / 71
librdkafkacpp.dll (cadef6d04660) - ## / 69
libssl-3-x64.dll (ad8438ee77b6) - ## / 73
Microsoft.AspNetCore.Grpc.JsonTranscoding.dll (6ce7f1e90be1) - ## / 73
Microsoft.Extensions.Caching.Memory.dll (a6bc869c530a) - ## / 72
Microsoft.Extensions.Options.dll (5e01894cbc06) - ## / 72
MongoDB.Bson.dll (a8090e419828) - ## / 72
MongoDB.Driver.dll (0aee1de11d14) - ## / 71
MurmurHash.dll (81e40968c215) - ## / 70
Namotion.Reflection.dll (f89768589a93) - ## / 71
NJsonSchema.Annotations.dll (db7a5c6a3ec0) - ## / 71
NJsonSchema.dll (544ff3a2d2af) - ## / 73
NJsonSchema.NewtonsoftJson.dll (cd0f77306810) - ## / 69
NodaTime.dll (494146cce9ce) - ## / 72
NodaTime.Serialization.SystemTextJson.dll (0d8b7fa02e3c) - ## / 72
OneOf.dll (2f0c32cb83ae) - ## / 74
Polly.Core.dll (37762ea6fcf0) - ## / 73
Polly.dll (361e6b1044c8) - ## / 73
Polly.Extensions.dll (8adac7a20cd0) - ## / 72
protobuf-net.Core.dll (da5535443676) - ## / 70
protobuf-net.Reflection.dll (abf0469c029f) - ## / 72
RabbitMQ.Client.dll (fda986194581) - ## / 73
RabbitMQ.Stream.Client.dll (aea88b127b0a) - ## / 64
Serilog.Enrichers.Environment.dll (fb988c77cc19) - ## / 75
Serilog.Formatting.Compact.dll (319fbcefc216) - ## / 73
Serilog.Settings.Reloader.dll (46e2d1919017) - ## / 70
Serilog.Sinks.Debug.dll (df543d3df8bd) - ## / 74
Serilog.Sinks.Seq.dll (7f1c18248d9c) - ## / 59
SharpCompress.dll (83a3a4076137) - ## / 73
Snappier.dll (efe89431b4fc) - ## / 73
System.CodeDom.dll (4d33e2986a84) - ## / 73
System.Interactive.Async.dll (75a516771f2e) - ## / 72
System.Reactive.Linq.dll (2e1ff9218438) - ## / 69
zlib1.dll (2a4ec31dfea7) - ## / 72
zstd.dll (90dd97ee000b) - ## / 73
ZstdSharp.dll (74ec06c67972) - ## / 73
EventStore.Diagnostics.LogsEndpointPlugin.dll (8341f64a4461) - ## / 73
EventStore.MD5.dll (b8472b741f73) - ## / 73
EventStore.OtlpExporterPlugin.dll (70c891b40b6c) - ## / 73
OpenTelemetry.Exporter.OpenTelemetryProtocol.dll (703aed9d8c31) - ## / 72
EventStore.Security.EncryptionAtRest.dll (5b2eeb2d3615) - ## / 73
EventStore.TcpPlugin.dll (a04a62d9d895) - ## / 67

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

Add to Builder	Version	Downloads	Last Updated	Status
	EventStore 24.10.1	7	Wednesday, December 18, 2024	Ready
	EventStore 24.10.0	14	Thursday, November 14, 2024	Approved

Release Notes

Program

Source code

Package

The chocolatey package unzips Event Store to the chocolatey install location.
Type EventStore.ClusterNode.exe to run the Event Store.

Dependencies

This package has no dependencies.

Discussion for the EventStore Package

Ground Rules:

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

21

14

14 Nov 2024

EventStore

EventStore 24.10.0

Some Checks Have Failed or Are Not Yet Complete

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

Program

Package

Ground Rules: