Could I deploy UI (Frontend) locally, not in your servers? Nicolas saying about
accessing our frontend directly on this machine
but I don’t understand what he talking about. Locally I can’t access anything but index page of Node Backend Server.
No, I want to make local deployment, but what’s the point if I cannot do anything with it without your remote UI? If I trying to enter in local projects in cloud UI, it says that it cannot get access to localhost. But I haven’t other UI.
If I understood correctly, UI absolutely unworkable without user-hosted backend, generated by lumber, and wrapped on SSL certs. I think you should create Docker image with completely workest example with Nginx and generated certificates (via certbot, for example).
Because when I, newbie, come to Forest Admin, I take your out-of-the-box deployments, with expectation to see how it works, without deep diving into. But it turns out that your “out-of-the-box” deployment is semi-workable - you need to wrap up Node with Nginx, or modify nodejs to install SSL-certs (and lumber and docs contains no word about this). Not all people every day installing nginx with SSL, and this “requirement” gonna be very annoying to their.
If I am wrong - let me know.
Hi @John 
That’s not totally correct.
As stated on the website, Forestadmin only provide the UI & the UI API in order to make your lumber generated backend work. The architecture of the solution assure that your data remains in your database.
The onboarding pages gives you all the needed commands to make it run on your local machine, assuming that port 3310 is available and database is accessible through the given database parameters.
The forest admin UI cannot work without a user-hosted backend, but it could totally be hosted locally and is able to request on localhost URL.
SSL/nginx/etc issues only appear when dealing with a remote/production environment (Localhost/127.0.0.1 should not cause any issues), since it is now a standard “webapp” requirement to run online apps with HTTPS.
In fact, since you provided your credential in the previous posts, I’m totally able to run a complete install on my local machine by just:
If you encounter any errors related to this process, let us know. We are all here to help you through this 
@Arnaud_Moncel, hi 
! Thanks for your reply 
Please, explain me, how I can deploy UI on local? I couldn’t find any info about UI local deploying in google and your docs! It seems like no one in the world know how to use Forest Admin locally!
I’ve deployed locally DB, Backend (by lumber) on 3310. Now I want to deploy Forest UI to use it locally.
You can’t/don’t have to deploy The forest UI locally, that’s the whole point of the architecture. Just connect to https://app.forestadmin.com, select your project, and you should be good to go.
In our architecture, we are responsible for hosting the forestadmin UI (Accessible through https://app.forestadmin.com). The UI connect to our API (For UI infos, stored in our end, like column visibility, charts positions, …) and your Admin API (generated by lumber) using a dynamic CORS mechanic.
The full onboarding steps should be:
If everything goes fine:
localhost
If not, you will probably have a stacktrace to share. That way, it’ll be easier for us to assist you.
Hi @John ,
Could you check this answer?
When creating a development environment, host have to be explicitly
localhostand be accessible viahttp. This is the only host Forest Admin allows without having to set
https, for security reasons; in a regular process, your development environment have to be local and accessible throughlocalhost. Then, after this local environment works, you would be able to create other environments (prodution, staging, etc.). But still they will require to be accessible throughhttpsonly.
In other words, you can have only use http://localhost:3310 but not http://84.201.173.76:3310 (without a s). If you follow exactly the steps provided by @Arnaud_Moncel, I guess your backend should be accessible via http://localhost:3310 . This step is important:
Run exactly the command given by the npm/docker process of your choice. When your lumber generated project is running locally (After npm/yarn start), https://app.forestadmin.com should detect that your installation is running.
After this step your backend should be accessible via http://localhost:3310 on your actual local computer and display this:
Yes, backend available from localhost. I’ve checked it by curl http://localhost:3310/
Thank you.
I’m not sure to understand what you did. Do you mean you checked on your local computer that it’s accessible thorugh http://localhost:3310 in your local computer browser?
You mentioned http://84.201.173.76:3310/ in your previous message.
Forest Backend is available on http://84.201.173.76:3310/
Is 84.201.173.76 a public address of your local computer? (i.e the one that you use to send the messages to this community). Could you confirm that (without using curl) you can access with your browser http://localhost:3310 (not using the distant IP, but explicitly localhost). I must be sure about that before investigating.
Lets forget about 84.201.173.76 (jopas_remote) for a minute. I deployed it on a local machine just now. I successfully completed project creation step. But I cannot enter the project:
This is jopas_local.
Eventually, I successfully deployed on local machine. Now I gonna try to do it on remote machine
I successfully passed creation step (I think trouble was on your side. May be a little server lag), but I got an issue when trying to enter the project jopas_remote2:
I strictly following an instruction of project creation. I’ve tried two times (jopas_remote and jopas_remote2) with the same result 
Hello @John
May I ask you the 6 last digits of the env_secret you are using for your project jopas_remote2 please ?
Thanks in advance 
Hi
8e37dd
…
Thanks @John 
The environment secret is correct, but !
I’ve seen that you are currently running three different projects (one local, two name with remote).
If I understand what you are trying to achieve, you would like to have your project accessible remotely, which is fine but here is the recommended procedure for this.
You successfully passed the first step, which is create a project on your local environment 
You should now use this one and use the feature: deploy to a remote. (go to your project settings, environments, you should see a button to deploy you project).
Deploy to a remote first.
You will guided by the UI on how to do it, just follow the steps, you will be given some new environment variables to use (a new environment secret for instance) in your remote instance.
Tell me if it helps 
Thx. But how I can solve the local deployment issue? I can’t enter the project at all 
I thought you successfully created on a local machine.
What’s the error you are encountering please ?
I getting the next pop-up when trying to click on project jopas_remote2 in UI:
Hi @John,
Thanks a lot for your patience, we’ll do our best to help you being all set up with all your environments.
As stated here, there seems to be a mismatch between the expected FOREST_ENV_SECRET key for your jopas_remote2 environment and the one available in the environment variables of the server hosting the lumber project.
You’ll need to go to the environment variables of the server hosting the lumber instance of your jopas_remote2 environment and replace it by the one you’ll find on your settings (project settings > environments).
Once that is done, you should be able to access your jopas_remote2 environment
I hope it helps
