Downloads:

1,915

Downloads of v 1.2.0:

189

Last Update:

31 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Kirill Osenkov

Tags:

copy sync compare files folder diff content

ContentSync

This is not the latest version of ContentSync available.

1.2.0 | Updated: 31 Jan 2016

Downloads:

1,915

Downloads of v 1.2.0:

189

Maintainer(s):

Software Author(s):

  • Kirill Osenkov

ContentSync 1.2.0

This is not the latest version of ContentSync available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall ContentSync, 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 contentsync -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 contentsync -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 contentsync installed
  win_chocolatey:
    name: contentsync
    state: present
    version: 1.2.0
    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 'contentsync' do
  action    :install
  version  '1.2.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: contentsync,
    Version: 1.2.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller contentsync
{
   Name     = 'contentsync'
   Ensure   = 'Present'
   Version  = '1.2.0'
   Source   = 'STEP 3 URL'
}

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


package { 'contentsync':
  provider => 'chocolatey',
  ensure   => '1.2.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install contentsync version="1.2.0" 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 by moderator gep13 on 31 Jan 2016.

Description

Like xcopy or robocopy, but doesn't touch destination files if byte contents are identical. Compares files based on content, not timestamp.


ContentSync.exe
md5: 7B92B8564ACDAEABF3F502D50ACB50BC | sha1: 2D8FBA5F26007130CCD586478E10B65E9207EF7D | sha256: 187905599458ED62D7DCFF176FCA0D16A386D249FE8FE455A093BBCE40B789CD | sha512: BB4A9C971E2EECF2477D768789B30E9744C90D82DFE8931CF9CFBCCB30011EA398DF43B709B530D3EFA65819E1DA33EBFE288AB05F67649A32CB5E7CA95D2A39

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
ContentSync 1.3.0 331 Wednesday, February 3, 2016 Approved
ContentSync 1.2.0 189 Sunday, January 31, 2016 Approved
ContentSync 1.1.0 254 Monday, January 25, 2016 Approved
ContentSync 1.0.0 232 Sunday, January 24, 2016 Approved

Minor remaining fixes and improved error reporting.


This package has no dependencies.

Discussion for the ContentSync Package

Ground Rules:

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