Deploying your changes

You're building a great feature which requires tweaking your layout (UI), you've used the Layout Editor and it knows looks just like you had imagined? Well now is the time to try it on a remote server!

Imagine this is your current situation:

Your branch my-branch is based on your origin environment (production in this case) and you have made layout changes (Δ) over it.

Applying your changes to production: deploy

deploy means applying your branch's changes to your origin environment definitively. To achieve this, you'll be using Forest CLI's deploy command:

forest deploy my-branch

The end result is the following:

Don't forget to deploy your backend changes as well (if any), as showcased on this flowchart.

Note how your layout changes are also applied to your remote, as it is based on production.

Testing your changes on a remote (i.e "staging") first: push

push means moving your branch's changes to a remote environment. To achieve this, you'll be using Forest CLI's push command:

forest push

Note that you'll be pushing your current branch. To select another branch, use switch.

Deploying from your remote's interface

Once you have tested your new feature on "Remote 1", you can't deploy your branch's layout to "Production", since your branch will have been deleted by pushing it to "Remote 1".

To deploy it from there, simply click on "Deploy to production" in the top banner!

Making changes directly from the remote

Imagine you've pushed your branch onto your remote, but notice a slight change is still required in the layout. Then, simply use the Layout Editor from your remote! It'll play nicely with your branch's layout changes: any changes you make on your remote will also be deployed when you run forest deploy.

Note that creating a branch from a remote's layout (in order to rework on it) is not possible at this time, but is definitely something we're considering.

If you would like to notify us of your interest in this feature, please submit your feedback here.