Introduction
Chef Supermarket is a collaborative cookbook repository. It has a searchable cookbook repository and a user-friendly web interface. Cookbooks in the Chef Supermarket are available to all Chef users.

The private Chef Supermarket is installed on the internal network behind a firewall. It behaves similarly to the public Chef Supermarket, with the exception of changing the location from which community cookbooks are maintained.
In this blog, we will briefly discuss what chef Private supermarket is. We will also see the installation and configuration of the Chef Private Supermarket.
Installation
The source code of the chef supermarket can be found on the below-mentioned links:
Supermarket Cookbook for Omnibus install
There are a few requirements for the Chef Supermarket. Let’s have a look at all of those requirements.
✴️ Operational Chef Infra Server, which serves as the OAuth 2.0 provider.
✴️ A chef infrastructure server user account with administrative rights.
✴️ A user account key for the Chef server.
✴️ A Linux host that is x86_64 compatible and has at least 2 GB of memory.
✴️ The hosts of the Chef Infra Server and Supermarket have synchronized their system clocks.
✴️ Having enough disc space on the server to accommodate the project's cookbook storage needs or having the necessary login information for an Amazon Simple Storage Service (S3) bucket.
We can install the Chef Supermarket with and without a cookbook.
To install the Supermarket with cookbook, we can use supermarket-omnibus-cookbook.
We can also install Supermarket without a cookbook. You can refer to the below-mentioned documentation to get more insights.
Install Supermarket With Cookbook
Install Supermarket without cookbook
After installing the Supermarket we can connect to it using the steps mentioned below.
Connect to Supermarket
Follow the instructions below to connect to the supermarket.
-
Enter the hostname for Chef Supermarket in the browser. If a certificate is not provided as part of the installation process, a private Chef Supermarket will produce and utilize a self-signed certificate (via the wrapper cookbook).
-
Accept the SSL certificate if it is displayed when connecting to Chef Supermarket via a web browser. For the private Chef Supermarket that is used in production, a reliable SSL certificate should be applied.
- Click the Create Account link after opening Chef Supermarket in a web browser. If the user is not already logged in, a prompt to log in to the Chef Infra Server is displayed. Give the Chef Supermarket permission to authenticate using the Chef Infra Server account.
Upgrade a Private Supermarket
You can upgrade a private supermarket using the steps mentioned below:
-
Close the server that runs Private Supermarket.
-
/var/opt/supermarket should be backed up.
-
Get the Chef Supermarket package.
-
Utilizing the proper package manager for your distribution, upgrade your system with the new package.
-
Reconfigure the settings using the below command on the server where Chef Supermarket is installed.
sudo supermarket-ctl reconfigure




