Staging can provide enhanced versatility when it comes to managing form and project deployments. By allowing for up to 10 different stages on a per project basis, users can now replicate a dev, stage, prod like workflow from within the Form.io platform itself.
Staging features are limited to projects with Team Pro and Enterprise level projects. If you do not have any projects with Team Pro or Enterprise level projects, you can still experience the full breath of Staging from within any Trial project.
To create a new stage, navigate inside of the project you wish extend.
Simply click the
+ New Stage tab at the top of the project.
In order to proceed, name the stage.
Add Stage button and the new stage will automatically be added to the active project.
Please note, each project can only support up to 10 different stages.
To edit a stage, including renaming or deleting a stage, click the settings button or the gear icon in the left navigation panel of the active project.
Stage Settings accordion panel users can rename, delete, or even protect a stage from modification.
Protected mode prevents the modification of any form or resource within that particular stage. Protected stages have a shield icon anchored to the left of the stage name making them easy to identify outside of the stage settings panel. Please note, the Live stage cannot be deleted or renamed.
Form.io allows users to push different forms though the staging pipeline by using Version Tags in the staging menu. Notice that that in this example, the Dev stage has a New Form
while the Staging stage does not.
The goal is to now push the New Form down the pipeline so that the Staging stage now has the Dev changes.
To do this, navigate into the project settings by clicking the settings or gear icon on the left navigation panel
and then select
Staging from the side menu. Next, select either
Create Version Tag or
Create to get started.
Label the version tag and then click
Create Version Tag.
Please note, the new form version automatically anchored itself to your active stage. In this example, notice that the Dev stage is now tagged 0.0.1.
Once a stage version has been defined, users can deploy the version to any stage.
Continuing with the example, select the Staging stage and using the staging panel, select the
0.0.1 version from the select version tag drop down menu and click
Deploy version tag to Stage.
Notice that the Staging stage now has the 0.0.1 version tag, mirroring the Dev stage.
This means that New Form is now available in our Staging stage, where as earlier it was not.
Finally, the stage can be deployed further down the pipeline to the Live stage. Please note, that since the Live stage was set as a protected stage earlier in this walk-through, using a stage deployment is the only way to make changes to the Live stage.
Beyond what has been illustrated above, staging can be used to role back an active stage to any previous iteration.