Repository cloning is included in all Enterprise plans and is available as an option on yearly Platinum plans. Reach out to our Sales team for more information.

We recommend using a staging environment for Prismic repositories if you are already in production and want to safely iterate on your codebase or update custom types.

This option allows you to clone the entirety of your production repository to a staging environment: copying all of the custom types, documents, and assets. The user-base remains independent, ensuring that only the relevant developers and content editors have access to the staging environment.

Once cloned, you can perform the necessary changes to your custom types, create new ones, and safely test them out in the staging environment of your codebase. Your staging application  can connect to the Prismic staging API endpoint.


FAQs:

  • How can I clone my production repository?
    Simply reach out to contact@prismic.io or, if you are on an Enterprise plan, directly to your customer success manager.
  • Should I use these environments for staging content?
    No, these environments are only meant for updating the codebase or custom types without jeopardizing the production repository.We recommend that content editors stay on the production repository to author new content. This is to simplify the authoring experience without having to push content from one environment to another and because migrating content from the staging repository to the production one is not ideal (see limitations of the  Import/Export tool for more about this).If you need to stage content safely, we recommend that you look into Content Releases.
  • How do I promote my changes from the staging environment to the production repository?
    To update an existing custom type, copy its JSON structure from the "JSON Editor" tab in the staging environment and paste it in its equivalent custom type in the production repository.
  • What happens if I delete/update a field when promoting a custom type from staging to production?
    You cannot rename the API ID of a field. More details here.
    If you want to remove a field, have a look at what happens here.
    If you're switching a "Rich text" field type into "Key text", read more about the behaviour here.
Did this answer your question?