Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

1,133

Downloads of v 0.0.1.26:

363

Last Update:

18 Feb 2017

Package Maintainer(s):

Software Author(s):

  • Sergey Ivasenko

Tags:

actors framework kino rendezvous

kino.Rendezvous.Service

This is not the latest version of kino.Rendezvous.Service available.

  • 1
  • 2
  • 3

0.0.1.26 | Updated: 18 Feb 2017

Downloads:

1,133

Downloads of v 0.0.1.26:

363

Maintainer(s):

Software Author(s):

  • Sergey Ivasenko

kino.Rendezvous.Service 0.0.1.26

This is not the latest version of kino.Rendezvous.Service available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install kino.Rendezvous.Service, run the following command from the command line or from PowerShell:

>

To upgrade kino.Rendezvous.Service, run the following command from the command line or from PowerShell:

>

To uninstall kino.Rendezvous.Service, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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

3. Copy Your Script

choco upgrade kino-rendezvous-service -y --source="'INTERNAL REPO URL'" --version="'0.0.1.26'" [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 kino-rendezvous-service -y --source="'INTERNAL REPO URL'" --version="'0.0.1.26'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install kino-rendezvous-service
  win_chocolatey:
    name: kino-rendezvous-service
    version: '0.0.1.26'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'kino-rendezvous-service' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.0.1.26'
end

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


cChocoPackageInstaller kino-rendezvous-service
{
    Name     = "kino-rendezvous-service"
    Version  = "0.0.1.26"
    Source   = "INTERNAL REPO URL"
}

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


package { 'kino-rendezvous-service':
  ensure   => '0.0.1.26',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator AdmiringWorm on 05 Mar 2017.

Description

Rendezvous service for kino networks


AsyncIO.dll
md5: B2792F73E2AE56711D8A9609150B680B | sha1: F4E8ECCCCC92F11A5A46A1D603882397403B536E | sha256: CE336909941800B36C92EA665444E4FCD41CA84D2B270B2FD4025C96C13187B3 | sha512: A55A854311ED136D359631F7B1726101C84BD07B52FE3065410E4CEF1905276BF888BB810CDEFFCA13B4214F161C30B878646FBC990246CDA0DBF1F4A249C7A3
Autofac.dll
md5: A64F880C56D1A14E549623A83135A6DE | sha1: E1E176012CF7F60D70FD14FD75A80F75B0CFB545 | sha256: 098574103733196678F582DC4AFFA29546D06AC58ACCE42FEF62BCF040284191 | sha512: A08D337A23FC7B30E73B3B3BC498DAF4A71B552585886C3A159171A0E8CEEA07B88E586249E564E224836D846B1B8719BC25F33438A90C1F437AF52D92B5FAF9
C5.dll
md5: 14D41EDE5DE0BEDD59066B673BEAC0E9 | sha1: 26570AFDF5E0F59592B5E0F4EBFEFBC1633B6302 | sha256: 4FF6ABC9A31866C6F79250AD52F82163E3BF84BAC3088FA7775E409E6A98C8AC | sha512: F7BA0012AFD0F0873A8BA493995056D3B02121FF5F1E389ECD7CAA5E5A8A2EF91D96E92B02F2AC66EF42BD59EB6309266E34F6558AEEBEF50A7E7E6024B35464
config\NLog.config
<?xml version="1.0" encoding="utf-8"?>

<!--layout="${longdate} [${level:uppercase=true}] ${message}"-->
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <targets async="true">
        <target xsi:type="File"
                name="file"
                fileName="${basedir}/logs/${shortdate}.log"
                layout="${message}" />
        <target xsi:type="EventLog"
                name="eventLog"
                layout="${longdate} [${level:uppercase=true}] ${message}"
                source="kino" />
        <target xsi:type="ColoredConsole"
                name="console"
                layout="${longdate} [${level:uppercase=true}] ${message}"
                useDefaultRowHighlightingRules="true">
        </target>
    </targets>

    <rules>
        <logger name="default" minlevel="Trace" writeTo="console, eventLog" />
    </rules>
</nlog>
config\RendezvousService.config.json
{
    "dev": {
        "rendezvous": {
            "broadcastUri": "tcp://127.0.0.8:8001",
            "unicastUri": "tcp://127.0.0.8:8011",
            "heartBeatInterval": "00:00:05"
        },
        "synod": {
            "localNode": "tcp://127.0.0.71:7000",
            "members": [
                "tcp://127.0.0.71:7000",
                "tcp://127.0.0.72:7000",
                "tcp://127.0.0.73:7000"
            ]

        },
        "lease": {
            "maxLeaseTimeSpan": "00:00:03",
            "clockDrift": "00:00:00.100",
            "messageRoundtrip": "00:00:00.400",
            "nodeResponseTimeout": "00:00:00.200"
        }
    }
}
kino.Connectivity.dll
md5: C99FAD93CB1A093EE49B3E73D0082740 | sha1: A6662B1BD4D3D33CD968DAB04430883121BC7B1C | sha256: 965372E0BBB6E9359A21FA6E914B4963AB6CDA4F087D31D668B2BD5FECD87023 | sha512: 788E79E1BA6FC2B2A852A929F833857EF134343DDBA4718AC3BC346AD688EB5467F130C5FDAC95C64BF17E3695B803343697CA9C0697E65E20CC4CE665888EB7
kino.Consensus.dll
md5: 4266479ABE8D5EDA8364893BD5B82916 | sha1: 77D9BD10B61F30C6422DFCB7267DABBC6A2E703B | sha256: 2280CB475547B47625A0EEFBFC1DA2B3F33F0808855CAA3534479D3BFC01F03C | sha512: 0823A7EEE51A6133877963CF442CF448D9B27BA23505BFE3431F19DDEB42EE25F99EF2B59C6B9C79E7EF28EF355A04ABB8B7A4AE0067C428352BAB84241FC538
kino.Core.dll
md5: 3A6CEDA0FD90F0B8F3254952E138D2B4 | sha1: 4D3C1F9FF3432A8BBE2BB34DDD10FF69E8F5751A | sha256: 0D7CC8D5EC7A999CA880F4A36E6C720313C25B13351FAED3DF6E39F0DD09C523 | sha512: EA3C37547857B13FB93ABE617FD08BD447E64E100444AB38970764E67C095AC4AFC0F9F0B97EC1FC5C067FB3E3F9ACA488B28EE47706F9887EB1E1061D333B22
kino.Messaging.dll
md5: 07E296BF2ACF621FD380B150D58A8323 | sha1: A5EB3C61B274B5909122C631994863AF56533E8A | sha256: 967051E1A77FA459D27191014C0FEFB28D7570B592AE0F8A72662C2C5640F794 | sha512: 4BC844B81068743C6E28A6ECBB7118E63AD5704AB12F2D7595DBBB6B1D8B8409A36019478AA05F5ABBA5F45E852EB105D6399CEFDC62237AD27856FC9C6C0501
kino.Rendezvous.dll
md5: E177D5CDC0C3F5D48BD92C14082E129F | sha1: DA90147E6EE433B7127F3109CED5BA933E69C451 | sha256: 6B88DD3EF3C146126846291543E15FFE6E828BA889A028E63677F1EFCD666B3A | sha512: 68C44A332B39AADC64C340136787295B4577C3A933A8A94B779391520ADFE1FA714822876AD81CC04C31AD17CFD8A06C4201CE01C66AEC21A91D1E81D03E04E6
kino.Rendezvous.Service.exe
md5: 7C4CB20321FBA91DA5506D7BA8D5910D | sha1: 9CE0FBEAC875B035C36D22929C7DA66E9940D516 | sha256: A1E04B5E370BD7DAF617325C3C47728427BB167AE9021A109A9BD56840C8EE19 | sha512: 2FAD94DCEA5134E4B96DFD9439FC0FAFADDEC9512F7B468A9CA368A1772C7EB557A4DEA5977AA9205342CC30D299AE577FF946D778DF56D78948683D238ECA0E
kino.Rendezvous.Service.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog" />
    </configSections>
    <appSettings>
        <add key="JsonConfig.EnvironmentSequence" value="DEV" />
    </appSettings>
    <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <include file="${basedir}/config/NLog.config" />
    </nlog>
    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="AsyncIO" publicKeyToken="44a94435bd6f33f8" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-0.1.20.0" newVersion="0.1.20.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-9.0.0.0" newVersion="9.0.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="protobuf-net" publicKeyToken="257b51d87d2e4d67" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-2.1.0.0" newVersion="2.1.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Autofac" publicKeyToken="17863af14b0044da" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.IO.Compression" publicKeyToken="b77a5c561934e089" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Security.Cryptography.X509Certificates" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Microsoft.Win32.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-4.0.1.0" newVersion="4.0.1.0" />
            </dependentAssembly>
        </assemblyBinding>
    </runtime>
<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.1" /></startup></configuration>
kino.Security.dll
md5: B546AA621E051DCC1208E67AC97D3DA9 | sha1: 2B43E15208BD2D5F335DDFE78032AA4A6B4E3034 | sha256: F3ACB88A8AF9378EEC63AE675B8AC3A4F266163CF91177D351E4FD5FC9EEF906 | sha512: 561B716A036422DE5FDD0642C48775BC518FC3E6978240EEC472B28F53F25563781EF2E79EA427DFF99D4441F1535CCFE0545E0D987E9B2259F7F9A9316F8292
NetMQ.dll
md5: E0D142B1301D8AFEC3D64FAE587B1383 | sha1: 59C72AF9D50F784874B92E6AC3ED567B875EA62D | sha256: CE9B347A4CF35C4ED96E1343F3CE84CE6514BE680347E59DE0F5A29F6EE6FBA1 | sha512: D50B803CDF4A400FEDAD355EF6B09352F8642B11104EA24A5F47F708DC2FA758A5165980EF8F10F50CD3C3EA6E1D97BBBB822C26AEE3ECDA5220A654A89E3560
Newtonsoft.Json.dll
md5: C53737821B861D454D5248034C3C097C | sha1: 6B0DA75617A2269493DC1A685D7A0B07F2E48C75 | sha256: 575E30F98E4EA42C9E516EDC8BBB29AD8B50B173A3E6B36B5BA39E133CCE9406 | sha512: 289543F5EEA472E9027030E24011BEA1E49E91059241FE6EB732E78F51822313E47D1E4769FA1C9C7D6139F6A97DCFEF2946836B3383E8643988BF8908162FB9
NLog.dll
md5: 617E856F82E68E873EE111C1A21CF3EE | sha1: A060907310C576ED14224E9EE59748C68F094B95 | sha256: 659572D0888327EC459FA8778842A7F0346FC5725BB5349CA66AE9990D23E869 | sha512: E6E4AEB6BC416937F5715237B8F77F0BFA19CE37FE86E27B8C1EFCA0E2A35086751D98D6D785FF5513998AF1B1C6E8C05064D84BD2F97D32EF7D11D280CC859A
protobuf-net.dll
md5: 0328D67FC2071670F11CE17970B8ECDA | sha1: 13625BDE59A49EE4A32DEB2AE73B4A34C7C408AB | sha256: 0EDF2382691A7706CFA740D95DA85830560AD006D038D7F70CDA6D745C872F85 | sha512: D706AE13C38E05A1680079375ABC9FDB20CBB400529F414A0A60669DF05E1ED2164214E59C2DAAD5445D1F43539614D0BCC082B632F01750779E792390D497F8
System.Reactive.Core.dll
md5: 39DBA19C792581D4B454D58E35878D86 | sha1: 08C83CE7CC2219C9BD80DEC9C6A42E8777F99E79 | sha256: EB0DED63A40EF4D8B2E2A78BCA52A8A8F74B8A2394867BB8547223B15AF380AA | sha512: 7F6241CE8B47C0AB91FB6AEBA509CF72B24C807C625DB5C75AA692452AC0DF025E8C14553C093FE979717634C63BEB07BED62AE313C5EFA814C9B53CF34FE712
System.Reactive.Interfaces.dll
md5: B80E8C6C63A953FC1258D28996B0CA8F | sha1: 161C6845C2663B574D226FDF9BDE0F256D72DDD6 | sha256: ED6131702DF41A1C2C4AB1027614BC028C61D54C3261D7090D43838A79BD9266 | sha512: 253834FBD6C121674B2AF71CB591E210563D18E29B8511FD854B25EEC52D5137DE66D03BBFD0B79AE7F4A2FFB8398CE7F68D99090F01F9A863E53EDEEC4F4F96
System.Reactive.Linq.dll
md5: 46DA475B75EE3F8DDE6D6541DCF7D9D2 | sha1: 47F67EE228FE6C201CD2C8E3F0F11D3983713B22 | sha256: C0689C2BBED77CD0595E7AF9EC42A0D49D8D5AF1CDAB736F16DD24BB95DF123B | sha512: E0082003D6B73EBAE7963C1BAE93F112CB24ADA68E492BCD776FC4288E49A0E2CF24401DC7B909AD60BBBA2390E941EE33514C00D1FA82219364AEDDAE63ED3F
TypedConfigProvider.dll
md5: 3CBC833E3717A2FAB3F647A22C3A2F7E | sha1: 888DFF5D39D1FFFB08BF40B57EA7724C558D3EAC | sha256: FF4001ADE25D059E3C7F0FE24930E65ADC4C1D1C9273CF51D2B51E80314F6B76 | sha512: 43C008763F13652747B88EE25A34C4F70F045CDBCB2701886D0B7EE21DA829CA058E8BA38FF2BDE7B9B8EA269620A599EC78BBBBB926B8C60CBFFD4A669C22EC
WindowsServiceHost.dll
md5: 21750666372BAE32A4D55E31E89D89E7 | sha1: 10A977EC6E73E86296649A572D1A4C74889E6938 | sha256: D370D4CEF5EF7974B509C2D6054F2560C7EFE14A3069808D98C40706006F81DE | sha512: FA7E09672F23545CB129EC57C8EF0632171930C55DABDDF398C4B35F35D23506C5F5F9A958A97BEDD76768E196A976886529B5E4C70F7DD3F80712D0F1BC970E

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.

Add to Builder Version Downloads Last Updated Status
kino.Rendezvous.Service 0.0.1.26 363 Saturday, February 18, 2017 Approved

This package has no dependencies.

Discussion for the kino.Rendezvous.Service Package

Ground Rules:

  • This discussion is only about kino.Rendezvous.Service and the kino.Rendezvous.Service 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 kino.Rendezvous.Service, 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