Notices: This section not yet converted to new layout. Download stats are rolling back out.

20

Downloads

12

Downloads of v 4.0.0.1

1/9/2017

Last update

1/9/2017

Published Date

EventStore

4.0.0.1

(Ready for review)

Package test results are passing.

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
  • Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
  • This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
  • You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
  • There are also no guarantees that it will be approved.

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

Review Comments:

geteventstore (maintainer) on 09 Jan 2017 13:20:26 +00:00:

User 'geteventstore' (maintainer) submitted package.

chocolatey-ops (reviewer) on 09 Jan 2017 13:52:40 +00:00:

eventstore-oss has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 09 Jan 2017 14:02:26 +00:00:

eventstore-oss has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/fb3a1911e48e7b154d610641167fbcea for details.
This is an FYI only. There is no action you need to take.

geteventstore (maintainer) on 09 Jan 2017 14:47:18 +00:00:

User 'geteventstore' (maintainer) submitted package.

chocolatey-ops (reviewer) on 09 Jan 2017 15:19:14 +00:00:

eventstore-oss has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 09 Jan 2017 15:23:07 +00:00:

eventstore-oss has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/fd8957233d435742b5332cbf6df7d7db for details.
This is an FYI only. There is no action you need to take.


The open-source, functional database with Complex Event Processing in JavaScript.

Files

Hide
  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    
    $len = $env:chocolateyPackageVersion.length
    $buildNumber=$env:chocolateyPackageVersion.Substring($len - 1, 1)
    $encodedVersion=[uri]::EscapeDataString("4.0.0-beta+$buildNumber")
    
    $packageName= 'eventstore-oss'
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $url        = "http://s3-eu-west-1.amazonaws.com/eventstore-binaries/binaries/$encodedVersion/windows/EventStore-OSS-Win-v$encodedVersion.zip"
    
    $packageArgs = @{
      packageName   = $packageName
      unzipLocation = $toolsDir
      url           = $url
    
      silentArgs    = "/qn /norestart /l*v `"$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log`""
      validExitCodes= @(0, 3010, 1641)
      
      softwareName  = 'EventStore'
    }
    
    Install-ChocolateyZipPackage @packageArgs
  • tools\chocolateyuninstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    
    $packageName= 'eventstore-oss'
    
    $len = $env:chocolateyPackageVersion.length
    $buildNumber=$env:chocolateyPackageVersion.Substring($len - 1, 1)
    $encodedVersion=[uri]::EscapeDataString("4.0.0-beta+$buildNumber")
    
    $packageName= 'eventstore-oss'
    $zipFileName= "/EventStore-OSS-Win-v$encodedVersion.zip"
    
    Uninstall-ChocolateyZipPackage $packageName $zipFileName

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Maintainer(s)

Software Author(s)

  • EventStore

Copyright

© 2017 Event Store LLP

Tags

Release Notes

Program

Package

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

Version History

Version Downloads Last updated Status
EventStore 4.0.0.1 12 Monday, January 9, 2017 submitted
EventStore 4.0.0-alpha1 8 Wednesday, January 11, 2017 exempted

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.

comments powered by Disqus