Created personal development environment but don't want to deploy yet

Help me!
1

Hi, Hopefully ok that I’m not following the issue template. Not sure I have an issue, just a “help me” question.

We have multiple users accessing our project. Each user should have their own development environment (as per some other posts, such as this).

The initial user has their development environment setup and working well. The second user has run though the forest init to setup their own development environment (with associated env vas etc). Now it has come time for the second user to do some dev work, however the UI says this development setup must be deployed before we can use it (see screenshot).

I’m not sure what this is going to happen if the second developer runs forest deploy, but reading through the documentation it seems like it will deploy “something” to production. But what will be deployed? The second developer hadn’t done anything yet.

Seems like a chicken or egg problem. How can the second developer start work without deploying to production or safely knowing they won’t cause anything to break in production.

Thanks!

image
image1548×848 66.9 KB

And, if you are self-hosting your agent:

  • Agent technology: nodejs,
  • Agent (forest package) name & version (from your .lock file): ^1.60.1
2

Hi @wilsonwaters and welcome to our community !

This user needs to run the agent with the new FOREST_ENV_SECRET, in order to be pushed in our server.
Don’t hesitate to reach out if the problem persists.

Best regards,

Shohan

3

Thanks Shohan,

Thanks for the tip. I had run the agent with the new FOREST_ENV_SECRET and refreshed the forest admin web app a number of times but for whatever reason it didn’t seem to be registering. I came back a few days later and the development environment had started showing in the list of environments with no further changes.

All good for now.

1 Like