Question #1: From this Environments doc, I see the way to create new environments. But currently this is not visible in my project. Is this a premium feature?
Question #2: There are certain configurations that I can do only from the ForestAdmin UI. Few examples are:
Displaying only few collections on the left hand side navigation bar
Setting description for a field
Ordering of fields in create/edit form
If I am using this Environments feature, how will I be able to sync the UI changes made in staging environment and automatically apply the same set of changes to production environment?
Creating new environments is not a premium feature, it’s available in our Community Plan. In order to be able to create new environments (remote or local for collaboration with other developers), you need to deploy your project to a production environment first and here’s a guide on that.
If you need more info on the different plans, please refer to our pricing page.
Once you have several environments, you will want to keep their layouts configurations synced. Let’s say you added some features in your local development environment, hid some collections, reordered some fields, etc. Now comes the time to copy the layout from “development” to “production”.
This is done in the environment settings tab, the whole operation takes a few seconds.
I could be wrong, but I think we made a change to the UI on production and now it’s out of sync with staging. Reading the help centre, it looks like updating the UI on production doesn’t save in the forestadmin-schema.json? If that’s the case I’m not sure why the environments are out of sync.
(please create a new topic for a specific question)
You are right about the UI update on production: this does not touch the forestadmin-schema.json. But keep in mind that forest UI changes made on production (with the layout editor) are reflected on the staging automatically. If this is not the case (if you do not see the production change on your staging), please create a new topic for this specific issue.
About the “source/destination schema” message while deploying: This message can happen when the destination (your production) is synchronizing (restarting), so giving a new try can make things work.
But a more possible reason is that you have a difference between the source/destination forestadmin-schema.json. To perform deploy or push operation, they must be equals.
To sync them, before deploying on the forest side, you have to deploy your staging server on your production server. This will sync your staging schema on the production schema, and then you will be able to perform the deploy on Forest.
If you need more help, please create a new topic on “source/destination” schema subject. At this time, please provide your project name.
