Deploying your changes

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

Imagine this is your current situation:

This would be the case if you chose "Staging" as the origin of your branch when you first created it. You have then made layout changes (Δ) over it.

Applying your changes to production: deploy

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

forest deploy

The 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"): push

Say, before you deployed to Production, you wanted to test your charges on a staging environment first.

push means moving your branch's changes to a remote environment set as the origin of your branch. 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. If the origin of your branch is not the remote you want (ie: staging) change it with set-origin

As your company grows, so does your development flow: you may want a more complex architecture where you have more than one layer of test environments before production (i.e preprod). This is possible using Forest CLI and the right environment settings, see here.

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.

You can also create a new branch with your remote environment as the origin and do the same process explained above.