About Environments

A publishing environment refers to one or more deployment servers or a content delivery destination (Webpage’s address) where you will publish your content (entries or assets).

Note: The environment is a global module that is available across all branches of your stack. Any environment that you create in the main branch, for instance, will be available in all the other branches of the stack. Refer to our Global Modules document for more information.

An environment allows users to publish their content on the destination URL. After you create an entry, you will publish it on an environment. After publishing, you will see the content on your website’s URL (specified in the environment). Being not limited to a single environment, you can publish content on multiple environments too.

For example, you have two servers of a website namely development and production. If you want to preview your content on your development server before publishing it on production, you can make two environments by specifying the URLs of these servers. Then, you can publish your content only on the development server. After the content looks correct on the development server, you can publish it on the production server.

Note: You can only be able to view the content on your website, after publishing, if you have configured the code that fetches data from Contentstack’s server.

The most common publishing environments used are development, staging, and production

Note: Contentstack no longer supports the ability to add multiple content deployment servers while setting up a specific publishing environment in Contentstack. We recommend that you instead make use of Webhooks to trigger deployment to multiple web servers whenever you publish content to an environment.

You can browse through the following topics, mentioned in the More Articles section below, to learn which actions you can perform on an environment.

Was this article helpful?