Downloads:

29,449

Downloads of v 0.1.4:

346

Last Update:

02 Jan 2018

Package Maintainer(s):

Software Author(s):

  • Rob Reynolds

Tags:

nuget odata iis repository chocolatey simple-server simple.server

Chocolatey Server (Simple)

This is not the latest version of Chocolatey Server (Simple) available.

0.1.4 | Updated: 02 Jan 2018

Downloads:

29,449

Downloads of v 0.1.4:

346

Software Author(s):

  • Rob Reynolds

Chocolatey Server (Simple) 0.1.4

This is not the latest version of Chocolatey Server (Simple) available.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Requires .NET Framework 4.6, which needs a reboot.

To install Chocolatey Server (Simple), run the following command from the command line or from PowerShell:

>

To upgrade Chocolatey Server (Simple), run the following command from the command line or from PowerShell:

>

To uninstall Chocolatey Server (Simple), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade chocolatey.server -y --source="'STEP 3 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 chocolatey.server -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure chocolatey.server installed
  win_chocolatey:
    name: chocolatey.server
    state: present
    version: 0.1.4
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'chocolatey.server' do
  action    :install
  version  '0.1.4'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: chocolatey.server,
    Version: 0.1.4,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller chocolatey.server
{
   Name     = 'chocolatey.server'
   Ensure   = 'Present'
   Version  = '0.1.4'
   Source   = 'STEP 3 URL'
}

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


package { 'chocolatey.server':
  provider => 'chocolatey',
  ensure   => '0.1.4',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install chocolatey.server version="0.1.4" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 02 Jan 2018.

Description

Chocolatey Server is a simple OData feed built on top of NuGet.Server.

Chocolatey Server builds on NuGet.Server with a few minor adjustments:

  • This is a packaged site, ready to deploy.
  • The apikey is already set.
  • There is more helpful information on the site when accessing locally:
    • There is a link to the Elmah logs
    • The api key is given on the page.
  • The location of packages defaults to a more secure location.

tools\chocolatey.server\App_Data\Packages\Readme.txt
To add packages to the feed put package files (.nupkg files) in this folder.
tools\chocolatey.server\bin\Elmah.dll
md5: 5F9FBA56E86C63D985C5108544EC5473 | sha1: 1C0452B49290CE5CC919CA18D76533B4C4267BDA | sha256: 24154C679DE6858BB53C03339FBBE275499280E7A6BC1F9E9586A72063EC6133 | sha512: 750344D705C99A18266F6C7CE21F38C4F42A1C25B9677FD7BB9009F7449CCE02F91033F9FF52AD9C1196C3B8053A42BFE1EB8DB61F755A20CECB3BEE33E7756F
tools\chocolatey.server\bin\HttpAuthenticationModule.dll
md5: C744A02CE9A66E017C921731C2B6D0B0 | sha1: 4154CE2453064D47A4FD4D368A6A56B8300BFE90 | sha256: B6264BF82760ABF5C941654D1964EC7092B17BDD98FA144311B6B1DECCE54222 | sha512: F1CA9D361120A622C068DE7E4D048E400F6D75954C451D9EEFC16BDC87B08393B6DEB7ED58C8EC93B909CB6C966C9AA520D3A7AA792EDF819BE8038C981C21B8
tools\chocolatey.server\bin\Microsoft.Web.Infrastructure.dll
md5: 969D6CAF273394F064475292D549516E | sha1: 91F688C235388C8BCEE03FF20D0C8A90DBDD4E3E | sha256: FE18F4259C947C1FD6D74F1827370E72D7AD09AEFB4B720AF227333583E0169F | sha512: B4F6A614E5FC52850E3D02EBF7E85ABF1EBE3FB4EBD6B4F03EC9DC4989CCE88E44714CA2198DD7E632F5ED0F15225A68B31052DA33E5AC3CE48A1C91C3C04446
tools\chocolatey.server\bin\Microsoft.Web.XmlTransform.dll
md5: 6AD7D1E92C9833F4BDDE6A4BC84F2E1A | sha1: B38D23B6A960F5F07664565835137FE3C8FDB7ED | sha256: 13DCF5066E00152238191314D4A46605204FFABDBB830BDD0C97DF3027D1261D | sha512: 01C4ECC46576618394FBBEE701F5A726F97D31FB39D5F1C6305D21CA7AD0B0ABC09B69FB733C42D4D1203FCE78DD3F3D5129C21EA0BC9B92D0AB3A7BF09C006C
tools\chocolatey.server\bin\Ninject.dll
md5: E090F92DC731060146786220AF8A789E | sha1: 0C824A1F33A1B15D08D6A084CD20008340BFD66B | sha256: 833DE781870630530BAA1AC3D86B614923F19A2C8EFA28E27992BE95AB0D8FD9 | sha512: B894DD3A1EF719CAEC569E2BC5BECEA460E882D1893F278981832658A9B866EC04862FE01552F6DB8D68CBDB48CA41FECE727915D2DA8F6F192B48128FF5EEE0
tools\chocolatey.server\bin\NuGet.Core.dll
md5: 4F31C0446B134A09C81CA92AEC561C02 | sha1: 119D6A1586170A7A07826AFE52A507951DBBDDA3 | sha256: 26CF936D35F4C3B2519BB8DC169EB83CB889CA2057C0F3FA8F9D9FD13AD8F45C | sha512: 52C9B5E0358031537A16EC1DB87373AAC7821060482B56F0B0524FEF304F50B8F7D8C136DFA68927D541144E1403FFBAED7DFDCCE8BD18970D97919EC48275DB
tools\chocolatey.server\bin\NuGet.Server.dll
md5: FA1A0A2D6355B9148FCAAACE89F0F38F | sha1: 06ADCE1052073F44FD986DED74DF43355AE63F14 | sha256: 611CD76BB18BCECF2B78BA0094774AC97C2705A83648375533B0CCD9A968753B | sha512: A83C4A1E7E2202DF1684FA2E558B7D4C273D3392342F69CA36E90C3E8DB618D2E1EA98B7A2417F6BE45D470F48B5510BF9425D0EE2207BE956783F59AA0E2C00
tools\chocolatey.server\bin\RouteMagic.dll
md5: E1FF5F59A4721B3DD1DCCF881971C39E | sha1: A7D57795CF6548891A35F82AA4EFBD4A45722614 | sha256: 6E646D8751758596A9DFCC41DEF59E33460CB6AB517F3796ECBEF935A29EA723 | sha512: E5CDF30CBFC648AA5346AD76713B2CAEE49ED8C899AA1479921A80D4E1A1A5FC35C4CA3DFA98D441698E4D011B6CEC6CBED868C8E3596DAD0EC619A8AAB11C5D
tools\chocolatey.server\bin\SimpleChocolateyServer.dll
md5: 07C95F00108CD3817FC8F79FDEED0953 | sha1: C6EDCD4F13F72652D673EA8866ABD87C9DE90E04 | sha256: DB57724EB7E7E28E28355DE625F283849E2DE9375E2235520C0CC8977626E6CF | sha512: B184A083DC7926C8C3892C4CAF8011B2A95BF511EB547AA8401E5C17DB179010AECDA225B4B710212D1F2E96B04E3F78980ABB80203FE5295C4B5A7843A08201
tools\chocolatey.server\bin\WebActivatorEx.dll
md5: E6EBF27FA68C47A434C2E6AC0C08CF5A | sha1: 113B4FBD946CD38A296FF07C6562A88676D7B79B | sha256: D3DA14B92659035996CB517E0A9001093780104F6018D56894355A53CF014900 | sha512: 2CBCDBDBE9C17A09173C36EF35AE4DECAC7D4AB54342E8443781E772C595CAA23E2735533E1BD330C4D6DA52574B3D281714514A35D988AC1E0A0BDD99948968
tools\chocolatey.server\Content\images\chocolatey.png
 
tools\chocolatey.server\Content\images\MarksUsePolicy.pdf
 
tools\chocolatey.server\DataServices\Packages.svc
 
tools\chocolatey.server\Default.aspx
 
tools\chocolatey.server\favicon.ico
 
tools\chocolatey.server\packages.config
<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="elmah" version="1.2.2" targetFramework="net40" />
  <package id="elmah.corelibrary" version="1.2.2" targetFramework="net40" />
  <package id="HttpAuthenticationModule" version="1.1" targetFramework="net40" />
  <package id="Microsoft.Web.Infrastructure" version="1.0.0.0" targetFramework="net40" />
  <package id="Microsoft.Web.Xdt" version="2.1.1" targetFramework="net40" />
  <package id="Ninject" version="3.0.1.10" targetFramework="net40" />
  <package id="RouteMagic" version="1.2" targetFramework="net40" />
  <package id="WebActivatorEx" version="2.2.0" targetFramework="net40" />
</packages>
tools\chocolatey.server\Web.config
<?xml version="1.0" encoding="utf-8"?>
<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=169433
  -->
<configuration>
  <configSections>
    <sectionGroup name="elmah">
      <section name="security" requirePermission="false" type="Elmah.SecuritySectionHandler, Elmah" />
      <section name="errorLog" requirePermission="false" type="Elmah.ErrorLogSectionHandler, Elmah" />
      <section name="errorMail" requirePermission="false" type="Elmah.ErrorMailSectionHandler, Elmah" />
      <section name="errorFilter" requirePermission="false" type="Elmah.ErrorFilterSectionHandler, Elmah" />
    </sectionGroup>
    <section name="httpAuth" type="HttpAuth.Configuration.HttpAuthSection,HttpAuthenticationModule" />
  </configSections>
  <system.web>
    <compilation debug="false" targetFramework="4.0" />
    <httpModules>
      <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah" />
      <add name="ErrorMail" type="Elmah.ErrorMailModule, Elmah" />
      <add name="ErrorFilter" type="Elmah.ErrorFilterModule, Elmah" />
      <add name="HttpAuthenticationModule" type="HttpAuth.HttpAuthenticationModule, HttpAuthenticationModule" />
    </httpModules>
    <httpRuntime executionTimeout="1200" maxRequestLength="2147482548" />
    <!-- <authentication mode="Windows|Forms|Passport|None">-->
    <authentication mode="None" />
  </system.web>
  <system.webServer>
    <security>
      <requestFiltering>
        <requestLimits maxAllowedContentLength="2147482548" />
      </requestFiltering>
    </security>
    <validation validateIntegratedModeConfiguration="false" />
    <modules runAllManagedModulesForAllRequests="true">
      <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah" preCondition="managedHandler" />
      <add name="ErrorMail" type="Elmah.ErrorMailModule, Elmah" preCondition="managedHandler" />
      <add name="ErrorFilter" type="Elmah.ErrorFilterModule, Elmah" preCondition="managedHandler" />
      <add name="HttpAuthenticationModule" type="HttpAuth.HttpAuthenticationModule, HttpAuthenticationModule" preCondition="managedHandler" />
    </modules>
    <staticContent>
      <mimeMap fileExtension=".nupkg" mimeType="application/zip" />
    </staticContent>
  </system.webServer>
  <elmah>
    <!--
        See http://code.google.com/p/elmah/wiki/SecuringErrorLogPages for 
        more information on remote access and securing ELMAH.
    -->
    <security allowRemoteAccess="false" />
    <errorLog type="Elmah.XmlFileErrorLog, Elmah" logPath="~/App_Data/Logs" />
  </elmah>
  <location path="elmah.axd" inheritInChildApplications="false">
    <system.web>
      <httpHandlers>
        <add verb="POST,GET,HEAD" path="elmah.axd" type="Elmah.ErrorLogPageFactory, Elmah" />
      </httpHandlers>
      <!-- 
        See http://code.google.com/p/elmah/wiki/SecuringErrorLogPages for 
        more information on using ASP.NET authorization securing ELMAH.

      <authorization>
        <allow roles="admin" />
        <deny users="*" />  
      </authorization>
      -->
    </system.web>
    <system.webServer>
      <handlers>
        <add name="ELMAH" verb="POST,GET,HEAD" path="elmah.axd" type="Elmah.ErrorLogPageFactory, Elmah" preCondition="integratedMode" />
      </handlers>
    </system.webServer>
  </location>

  <location path="api/v2/package">
    <system.web>
      <authorization>
        <allow users="?" />
      </authorization>
    </system.web>
  </location>
  <appSettings>
    <!--
            Determines if an Api Key is required to push\delete packages from the server. 
    -->
    <add key="requireApiKey" value="true" />
    <!-- 
            Set the value here to allow people to push/delete packages from the server.
            NOTE: This is a shared key (password) for all users.
    -->
    <add key="apiKey" value="chocolateyrocks" />
    <!--
            Change the path to the packages folder. Default is ~/Packages.
            This can be a virtual or physical path.
        -->
    <add key="packagesPath" value="~/App_Data/Packages" />
    <!--
            Set allowOverrideExistingPackageOnPush to false if attempts to upload a package that already exists
            (same id and same version) should fail.
    -->
    <add key="allowOverrideExistingPackageOnPush" value="false" />
    <!--
            Set enableDelisting to true to enable delist instead of delete as a result of a "nuget delete" command.
            - delete: package is deleted from the repository's local filesystem.
            - delist: 
              - "nuget delete": the "hidden" file attribute of the corresponding nupkg on the repository local filesystem is turned on instead of deleting the file.
              - "nuget list" skips delisted packages, i.e. those that have the hidden attribute set on their nupkg.
              - "nuget install packageid -version version" command will succeed for both listed and delisted packages.
                 e.g. delisted packages can still be downloaded by clients that explicitly specify their version.
    -->
    <add key="enableDelisting" value="true" />
    <!--
      Set enableFrameworkFiltering to true to enable filtering packages by their supported frameworks during search.
    -->
    <add key="enableFrameworkFiltering" value="false" />
    <!--
      Turns off ASP.NET's built in simple membership provider
    -->
    <add key="enableSimpleMembership" value="false" />
  </appSettings>
  <!-- 
    HttpAuth Module
    Mode - {None|Basic|Digest}
    Realm - {Plain|Secret|<Pick some value>}
    Source - {Inline|FormsAuthentication|MembershipProvider}
    PasswordFormat - {Clear|SHA1|MD5|MD5Digest} - MD5Digest only with Digest mode
      [ <user name="user name" password="password" />
        [<user name="..." password="..."/>]
        [...]
      ] 
    </credentials>
  </httpAuth>
  -->
  <httpAuth mode="Basic" realm="Chocolatey Simple Server">
    <!-- To turn this on, you need to deny unknown users to the chocolatey path. See authorization in the system.web section below -->
    <credentials source="Inline" passwordFormat="Clear">
      <user name="choco" password="rocks" />
      <!-- add users here -->
    </credentials>
  </httpAuth>
  <location path="chocolatey">
    <system.web>
      <authorization>
        <!-- change this to deny to turn on basic auth -->
        <allow users="?" />
      </authorization>
    </system.web>
  </location>
  <system.serviceModel>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
  </system.serviceModel>
</configuration>
tools\chocolateyInstall.ps1
$packageName = 'chocolatey.server'

try { 
  $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  $webToolsDir = Join-Path $toolsDir $packageName
  $installDir = Get-BinRoot
  $webInstallDir = Join-Path $installDir $packageName
  
  #Enable Web Services
  #cinst IIS-WebServerRole -source WindowsFeatures
  #cinst IIS-ISAPIFilter -source WindowsFeatures
  #cinst IIS-ISAPIExtensions -source WindowsFeatures
  
  # https://github.com/chocolatey/chocolatey/wiki/DevelopmentEnvironmentSetup
  # cinst ASPNET -source webpi
  # cinst ASPNET_REGIIS -source webpi
  # cinst DefaultDocument -source webpi
  # cinst DynamicContentCompression -source webpi
  # cinst HTTPRedirection -source webpi
  # cinst IIS7_ExtensionLessURLs -source webpi
  # cinst IISManagementConsole -source webpi
  # cinst ISAPIExtensions -source webpi
  # cinst ISAPIFilters -source webpi
  # cinst NETExtensibility -source webpi
  # cinst RequestFiltering -source webpi
  # cinst StaticContent -source webpi
  # cinst StaticContentCompression -source webpi
  # cinst UrlRewrite2 -source webpi

  # W3SVC should be running
  
  # http://msdn.microsoft.com/en-us/library/windows/desktop/ms724832.aspx
  $osVersion = [Environment]::OSVersion.Version
  if ($osVersion -ge [Version]'6.2') #8/2012+
  {
    #cinst IIS-NetFxExtensibility45 -source WindowsFeatures
    #cinst NetFx4Extended-ASPNET45 -source WindowsFeatures
    #cinst IIS-ASPNet45 -source WindowsFeatures
   
  } else { #Windows 7/2008 and below
    ."$env:windir\microsoft.net\framework\v4.0.30319\aspnet_regiis.exe" -i
  }
  
  #TODO: if exists, copy the App_Data folder somewhere else for a moment so stuff doesn't get deleted
  
  Copy-Item $webToolsDir $webInstallDir -recurse -force
 
 
  #Import-Module WebAdministration
  #Remove-WebSite -Name "Default Web Site" -ErrorAction SilentlyContinue
  #Remove-WebSite -Name "ChocolateyServer" -ErrorAction SilentlyContinue
  #New-WebSite -ID 1 -Name "ChocolateyServer" -Port 80 -PhysicalPath "$webInstallDir" -Force

  # $networkSvc = 'NT AUTHORITY\NETWORK SERVICE'
  # Write-Host "Setting folder permissions on `'$webInstallDir`' to 'Read' for user $networkSvc"
  # $acl = Get-Acl $webInstallDir
  # $acl.SetAccessRuleProtection($False, $True)
  # $rule = New-Object System.Security.AccessControl.FileSystemAccessRule("$networkSvc","Read", "ContainerInherit, ObjectInherit", "None", "Allow");
  # $acl.AddAccessRule($rule);
  # Set-Acl $webInstallDir $acl  
  
  # $webInstallAppDataDir = Join-Path $webInstallDir 'App_Data'
  # Write-Host "Setting folder permissions on `'$webInstallAppDataDir`' to 'Modify' for user $networkSvc"
  # $acl = Get-Acl $webInstallAppDataDir
  # $acl.SetAccessRuleProtection($False, $True)
  # $rule = New-Object System.Security.AccessControl.FileSystemAccessRule("$networkSvc","Modify", "ContainerInherit, ObjectInherit", "None", "Allow");
  # $acl.AddAccessRule($rule);
  # Set-Acl $webInstallAppDataDir $acl
  # 
  # Import-Module WebAdministration
  # $appPoolPath = "IIS:\AppPools\$projectName"
  # #$pool = new-object
  # Write-Warning "You can safely ignore the next error if it occurs related to getting an app pool that doesn't exist"
  # $pool = Get-Item $appPoolPath
  # if ($pool -eq $null) {
  #   Write-Host "Creating the app pool `'$appPoolPath`'"
  #   $pool = New-Item $appPoolPath 
  # }
  # 
  # $pool.processModel.identityType = "NetworkService" 
  # $pool | Set-Item
  # Set-itemproperty $appPoolPath -Name "managedRuntimeVersion" -Value "v4.0"
  # #Set-itemproperty $appPoolPath -Name "managedPipelineMode" -Value "Integrated"
  # Start-WebAppPool "$projectName"
  # Write-Host "Creating the site `'$projectName`' with appPool `'$projectName`'"
  # New-WebApplication "$projectName" -Site "Default Web Site" -PhysicalPath $srcDir -ApplicationPool "$projectName" -Force

  #Client SKUs need to enable firewall
  #netsh advfirewall firewall add rule name="Open Port 80" dir=in action=allow protocol=TCP localport=80

  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" "$($_.Exception.Message)"
  throw
}
tools\LICENSE.txt
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
tools\VERIFICATION.txt
Chocolatey Server is from Chocolatey Software, and we maintain the package.

Log in or click on link to see number of positives.

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 Downloads Last Updated Status
Chocolatey Server (Simple) 0.2.5-beta-20180418 351 Wednesday, April 18, 2018 Approved
Chocolatey Server (Simple) 0.2.4 2189 Monday, February 26, 2018 Approved
Chocolatey Server (Simple) 0.2.3 511 Sunday, February 11, 2018 Approved
Chocolatey Server (Simple) 0.2.2 771 Thursday, January 11, 2018 Approved
Chocolatey Server (Simple) 0.2.1 330 Monday, January 8, 2018 Approved
Chocolatey Server (Simple) 0.2.0 386 Thursday, January 4, 2018 Approved
Chocolatey Server (Simple) 0.1.4 346 Tuesday, January 2, 2018 Approved
Chocolatey Server (Simple) 0.1.3 1264 Friday, October 6, 2017 Approved
Chocolatey Server (Simple) 0.1.2 2632 Thursday, November 17, 2016 Approved

0.1.4

BUG FIXES

  • Fix - Turning on basic auth in web.config doesn't allow pushing packages

IMPROVEMENTS

  • Use Chocolatey icon for favicon

0.1.3

FEATURES

  • Allow specifying Basic Authentication credentials directly from the web.config file.

IMPROVEMENTS

  • Increase timeout for pushing packages from the default of 110 seconds to 1200
    seconds (20 minutes).

0.1.2

IMPROVEMENTS

  • Package size allows for 2GB
  • Uses same NuGet enhancements that Chocolatey uses.

0.1.1

BUG FIXES

  • Small fix to not do anything with respect to making changes.

IMPROVEMENTS

  • Cleaned up files

0.1.0

  • Initial Release
Discussion for the Chocolatey Server (Simple) Package

Ground Rules:

  • This discussion is only about Chocolatey Server (Simple) and the Chocolatey Server (Simple) 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 Chocolatey Server (Simple), 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.
comments powered by Disqus