environments:reset
Please be sure of your agent type and version and pick the right documentation accordingly.
This is the documentation of the forest-express-sequelize and forest-express-mongoose Node.js agents that will soon reach end-of-support.
forest-express-sequelize v9 and forest-express-mongoose v9 are replaced by @forestadmin/agent v1.
Please check your agent type and version and read on or switch to the right documentation.
This is still the latest Ruby on Rails documentation of the forest_liana agent, you’re at the right place, please read on.
This is the documentation of the django-forestadmin Django agent that will soon reach end-of-support.
If you’re using a Django agent, notice that django-forestadmin v1 is replaced by forestadmin-agent-django v1.
If you’re using a Flask agent, go to the forestadmin-agent-flask v1 documentation.
Please check your agent type and version and read on or switch to the right documentation.
This is the documentation of the forestadmin/laravel-forestadmin Laravel agent that will soon reach end-of-support.
If you’re using a Laravel agent, notice that forestadmin/laravel-forestadmin v1 is replaced by forestadmin/laravel-forestadmin v3.
If you’re using a Symfony agent, go to the forestadmin/symfony-forestadmin v1 documentation.
Please check your agent type and version and read on or switch to the right documentation.
environments:reset
The forest environments command is very useful as it allows you to manage your environments. But the sub command that we're more specifically interested in when it comes to developing on Forest Admin is:
$ forest environments:reset --help
Reset a remote environment by removing all layout changes
USAGE
$ forest environments:reset
OPTIONS
-e, --environment=environment The remote environment name to reset.
-p, --projectId=projectId The id of the project to work on.
--force Skip reset changes confirmation.As you've learnt in previous pages, the forest push command lets you push changes made in the layout to a remote environments and later deploy them to your production.
Sometimes though, there comes a time when you've stacked too many layout changes on a remote environment and just want to get rid of them.
Unlike a branch which you can just dispose of, for a remote environment you need a way to clean it easily, this is where the forest environments:reset command comes in.
Last updated
Was this helpful?