Hello @timothyarmes, and welcome to our community
forest-cli, the generated
.gitignore ignore the
.env, and it’s the expected behavior.
FOREST_AUTH_SECRET is used for the authentication process, and should be kept secret (And, for security purposes, different for every environment). You can set it to whatever you’d like, and it’s not a value that forest can access.
FOREST_ENV_SECRET however, is related to the current environment you are using. When deploying remote (Either staging or production environment), the forestadmin UI will give you new values for this environment variable.
You should also be able to create new development environment, either using
forest-cli, or the
Project settings > Environments tabs from the UI. This value can be seen as an API Key, and should not be shared. You should be able to read more infos about this here. A ForestAdmin project will most likely have multiple environments. Usually, one environment per developers, remote environment as you need them, and one production environment.
You can also read this part of the documentation about our development workflow, that contains a few commands to help onboard new developers on a projects, as well as collaborative work on your forestadmin UI layout.
Let me know if it was enough, or if you need more details