Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.

If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping

Answers may be delayed for posts that do not include sufficient information.

Versioning Configurations Across Environments

Hi Everyone,

I'm a fresh Collective Access user and I was wondering if there was any way to version over configurations, e.g. the structure of menus, objects, etc... across all environments (local, staging, live) by versioning them via git. I've noticed that there is an app/conf/local folder in which there are several files including app.conf. When adding these files to git and pull them into a separate environment I notice that none of the changes come into effect, notably the menu structure remains the same.

Is there any way to version and standardize configuration across all environments?


  • Yes, it's possible to spin up another version of a configuration. You'll need to include all the configuration files (those in /app/conf/local as well as any printTemplates, messages files for translations, etc.), any themes and/or graphics (if relevant, themes are not frequently customized for Providence) and the installation profile.

    Are all of these elements included in your new environment? Have all of the local configuration files been pulled over?

Sign In or Register to comment.