https://cinc.sh/ Recent content in Home on CINC Hugo -- gohugo.io Fri, 06 Dec 2024 22:00:33 +0100 https://cinc.sh/start/server/ Wed, 20 Apr 2022 09:43:22 -0700 https://cinc.sh/start/server/ Server Installation Install using the install script As with upstream packages, you can use the install script method described in upstream documentation. Simply substitute the URL with https://omnitruck.cinc.sh/install.sh. For example, to install the latest 15.x of cinc-server on a supported platform: curl -L https://omnitruck.cinc.sh/install.sh | sudo bash -s -- -P cinc-server -v 15 Install from plain packages Packages are on our download site. We have packages available for all default package managers for platforms we support. https://cinc.sh/start/client/ Fri, 10 Apr 2020 15:31:30 -0500 https://cinc.sh/start/client/ Client Installation Install using the install script As with upstream packages, you can use the install script method described in upstream documentation. Simply substitute the URL with https://omnitruck.cinc.sh/install.sh. For example, to install the latest 18.x of Cinc Client on a supported UNIX/Linux/MacOS platform: curl -L https://omnitruck.cinc.sh/install.sh | sudo bash -s -- -v 18 For Windows: . { iwr -useb https://omnitruck.cinc.sh/install.ps1 } | iex; install -version 18 Install using bundler We publish gem packages to our Gem in a Box instance running at https://rubygems. https://cinc.sh/start/workstation/ Fri, 10 Apr 2020 15:31:30 -0500 https://cinc.sh/start/workstation/ Workstation Install Install using the install script As with upstream packages, you can use the install script method described in upstream documentation. Simply substitute the URL with https://omnitruck.cinc.sh/install.sh. For example, to install the latest 24.x of Cinc Workstation on a supported UNIX/Linux/MacOS platform: curl -L https://omnitruck.cinc.sh/install.sh | sudo bash -s -- -P cinc-workstation -v 24 For Windows: . { iwr -useb https://omnitruck.cinc.sh/install.ps1 } | iex; install -project cinc-workstation -version 24 Install from plain packages Packages are on our download site. https://cinc.sh/goals/ Mon, 01 Jan 0001 00:00:00 +0000 https://cinc.sh/goals/ The Cinc projects defines two goals for itself. 1. Making Chef Software Inc’s open source products easily distributable, by anyone We’re not just building a distribution, we are making the software distributable! We are doing so by submitting changes directly upstream. These changes are designed to make it simple for anyone to create their own distribution of these products. As an example, in https://github.com/chef/chef we have created a file called dist. https://cinc.sh/start/auditor/ Fri, 10 Apr 2020 15:31:30 -0500 https://cinc.sh/start/auditor/ Auditor Install Install using the install script As with upstream packages, you can use the install script method described in upstream documentation. Simply substitute the URL with https://omnitruck.cinc.sh/install.sh. For example, to install the latest 6.x of Cinc Auditor on a supported UNIX/Linux/MacOS platform: curl -L https://omnitruck.cinc.sh/install.sh | sudo bash -s -- -P cinc-auditor -v 6 For Windows: . { iwr -useb https://omnitruck.cinc.sh/install.ps1 } | iex; install -project cinc-auditor -version 6 Install using bundler We publish gem packages to our Gem in a Box instance running at https://rubygems. https://cinc.sh/download/ Mon, 01 Jan 0001 00:00:00 +0000 https://cinc.sh/download/ Omnibus Installer Cinc Client, Auditor and Workstation can be programmatically installed using https://omnitruck.cinc.sh/install.sh (Unix-like systems) or https://omnitruck.cinc.sh/install.ps1 (Windows systems) as you would do for an omnibus install of Chef. You can find detailed instructions in the “getting started” section. Download plain packages You can find our packages here. Package repositories We don’t currently have repositories for standard package managers like yum or apt but we’re looking for design proposals. EULA Compliance The following board shows the versions after which the Cinc Project considers the product releases to be compliant with the Chef Policy on Trademarks. https://cinc.sh/contributing/ Mon, 01 Jan 0001 00:00:00 +0000 https://cinc.sh/contributing/ Working upstream Most of the work should be happening in Chef Software’s repository. As such, anyone can contribute to Cinc’s efforts without direct involvement in the project. We have design documents on many upstream repositories detailing how we’re implementing simpler redistribution under configurable names. Anyone can read and open pull requests directly upstream to implement the design documents. Our Build Pipelines Our build and release processes should be 100% automated, that means pipelines! https://cinc.sh/blog/cinc_as_highly_available_cluster/ Fri, 06 Dec 2024 22:00:33 +0100 https://cinc.sh/blog/cinc_as_highly_available_cluster/ Introduction For most use cases a single instance of CINC will cover all your needs. It is a tool after all, and not a service that processes client traffic. But, if for some of you out there, having a single instance of anything is not acceptable, or if in your infrastructure CINC plays a crucial role, there is a way to have CINC in a highly available clustered setup. In this article we will go through setting up this on VM’s in your private cloud or with some cloud provider. https://cinc.sh/blog/migrating_from_chef_to_cinc/ Mon, 05 Feb 2024 10:42:00 +1000 https://cinc.sh/blog/migrating_from_chef_to_cinc/ Intro Many users already in the Chef ecosystem may have reason to migrate from Chef Infra Server to Cinc server. Thankfully, this is a relatively painless process and all cookbooks, users, data bags, roles, environments, etc. can be retained during the migration process. This blog post documents the migration process from Chef Infra Server to Cinc Server in Red Hat Enterprise Linux 8. Cinc Server Setup In order to create your new Cinc Server, stand up a new server on your OS of choice by following the steps detailed at Server Installation. https://cinc.sh/blog/products_alternatives/ Thu, 02 Nov 2023 21:48:55 -0400 https://cinc.sh/blog/products_alternatives/ Here’s the short list of changes people migrating solutions can expect to look into (updated 2023-11-02): Chef Infra™ client –> Cinc-client Chef Infra™ server –> Cinc-server or Goiardi Chef Inspec™ –> Cinc-auditor Chef Habitat™ –> see Cinc-project friends biome.sh Cinc’s own Habitat distro is considered low priority by the project in the presence of such a great alternative. Chef Workstation –> Cinc-Workstation Chef Automate -> Looking for contributors to help building it. https://cinc.sh/blog/cinc-server/ Wed, 20 Apr 2022 14:07:31 -0700 https://cinc.sh/blog/cinc-server/ Thanks to our various contributors, we are excited to announce that Cinc Server 14.14.1 is the first release that is now considered stable! You can find additional information on how to install and use Cinc Server here. https://cinc.sh/blog/cinc-and-dokken/ Wed, 01 Dec 2021 14:44:33 +0800 https://cinc.sh/blog/cinc-and-dokken/ Why use Kitchen Dokken? In a word, speed. The kitchen-dokken plugin is designed to make testing your Cinc/Chef code as fast as possible. As you can probably determine from the name, the plugin uses containers to speed up the process, both for the OS being provisioned and for the Cinc/Chef client. There are of course some trade-offs required to achieve this speed, firstly the plugin is Chef/Cinc specific (not really an issue if you are reading this! https://cinc.sh/blog/dist_2_0/ Sun, 10 May 2020 12:41:55 -0400 https://cinc.sh/blog/dist_2_0/ The short version This blog post is intended specifically for other folks that are building their own distributions of Chef Software’s product, and folks leveraging the tip from my previous blog in their cookbooks. We’re preparing to completely rewrite the current implementation of dist.rb in both Chef Infra and Chef Inspec. The short version is that we’re moving all the constants like Chef::Dist::PRODUCT to a new namespace and gem, respectively ChefUtils::Dist in the chef-utils gem. https://cinc.sh/blog/april_2020_update/ Fri, 03 Apr 2020 21:48:55 -0400 https://cinc.sh/blog/april_2020_update/ What’s new with Cinc? We’ve been busy! Since my last post in january, the team has not only kept up with releases of Cinc-Client and Cinc-Auditor but also improved many aspects of the project. With the release of Chef Infra 16 approaching fast, we’ve started getting Cinc-Client 16 builds ready. There’s also been significant work on our Cinc-Workstation pipeline, which now outputs artifacts of all but Windows builds, and those are in progress too. https://cinc.sh/blog/cooking_with_cinc/ Tue, 28 Jan 2020 15:31:30 -0500 https://cinc.sh/blog/cooking_with_cinc/ So what’s cooking? As part of a private project I’m looking to deploy a Goiardi server, and what better way to do so than with Cinc Client? My first stop was, as always, the Chef Supermarket, where one can find excellent cookbooks to feed into Cinc. There I found this cookbook by Matt Whiteley. It’s a little bit dated, but that’s an easy issue to solve; We’ll update it! The new trend in community cookbooks is to write ‘resource cookbooks’, that is cookbooks that define custom resources and libraries but no recipes. https://cinc.sh/blog/cinc_client_is_live/ Wed, 04 Dec 2019 16:05:34 -0500 https://cinc.sh/blog/cinc_client_is_live/ The Cinc project is proud to announce the initial release of Cinc Client It’s been a long time coming, but the Cinc team is finally ready to announce it’s first official release of Cinc Client for Linux. While we have been distributing it for some time, it came with all kinds of disclaimers about compliance with Chef Software’s policy on trademarks. No longer! Chef Software has reviewed Cinc Client and deemed it compliant with it’s policy as reported on Chef’s Community Slack.