I added a customHosting=true, still asking for creating a project
https://app.forestadmin.com/projects/create/setup/1?customHosting=true
Also, the back button is disabled. I want to setup my existing project in my development environment using node.js but I am unable to do. Please help me to setup it
Hello @alfaizm,
You can access all your projects following this link https://app.forestadmin.com/projects
You’re currently simply on a new project creation, the query parameter you have added is indeed the correct one to enable hosting choice, which will be prompted on the next step.
After you’ve confirmed this on your already existing project, could you please share its name so I can ensure that it isn’t wrongly flagged as Cloud setup.
Best regards,
HI @dogan
My project name is Shades of Spring Cloud and this is my project id 126470. Now I want to implement a custom user dashboard in the node.js application but I am unable to do so. I tried to setup the project as per given steps on this link. Its asking for the AUTH & ENV secret.
FOREST_AUTH_SECRET=
FOREST_ENV_SECRET=
NODE_ENV=development
Please let me know. If these steps are correct and if not then guide me to setup the project on my local
From what I can see, this is a long lived Cloud project. I’m guessing you’re not trying to create a new self-hosted project, but an environment on which you can develop and test locally before pushing it to your production environment which is hosted by us.
If that is indeed the case, you can find all the steps to do so inside of the Forest Admin UI on the lower left side of the screen:
Hi @dogan
Please check the screenshot. This is my GitHub repository where I have added all the custom fields in the code.
Now, I want to create a new project in Forest Admin and connect it to this GitHub repository.
Previously, I had a Forest Admin project named Shades of Spring, which was connected to this GitHub code, but it is no longer working.
I would now like to create a new Forest Admin project and link it with the same GitHub repository.
Could you please guide me through the steps to do this?
Here is a step by step to achieve what you want:
?customHosting=true you will then be able to choose the hosting choice.env of your existing repository.Next step in the UI@dogan.ay - We did all these steps but unable to get anything like this
Hello @nidhi_gupta,
Could you please provide some screens or informations on where you are encountering issues ?
If you are willing we could also schedule a call to help you sort things faster.
Best regards,
Hi @dogan.ay Can we connect on the call to discuss. Please share the meeting invite on this email khalid@aliqan.com
Hello @alfaizm, I have just sent you an invite, I am currently in the room if you are not available, I can send you a link to book a call in my calendar.
hello @nidhi_gupta, sorry for the late reply.
Could you share the network tab of your browser when you’re receiving those calls on your agents. Are there any errors ?
When the UI awaits your “backend to run”, you may encounter issues related to your browser or some extensions that could block the calls/responses. Could you try, if you’re not using it, Google Chrome with all extensions disabled. If not what is your current browser and version number ?
Yes, its throwing 404 error, the forestadmin is looking for the forest route which is not there as we are using the API which start from /api/*
The /forest endpoint is defined by the agent, it is similar to a /healthcheck call. Can you do a curl on your agent on the /forest endpoint to ensure it is accessible ?
@dogan.ay I was looking in a different repository. I’ve now found the correct one where the /forest root is defined. However, some environment variables are missing, and I’m unable to find them in Forest Admin either. Could you please look into this?
process.env.CORS_ORIGINS
process.env.APPLICATION_PORT
process.env.PORT
process.env.DATABASE_URL
process.env.CORS_ORIGINS
Not necessary if you do not have a customDomain
process.env.APPLICATION_PORT
Should be the port on which you start your agent, on the screen you have shared, this should be set to 3000
process.env.PORT
Not exploited by our agent
process.env.DATABASE_URL
Should be the URL address of the database the agent will connect to
