Install Forest Admin on a remote machine
Last updated
Last updated
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.
In this short tutorial, we'll cover how to install Forest Admin on a remote environment instead of locally.
This is not the recommended way of using Forest Admin.
When you install Forest Admin, on the last step you are asked to run some commands:
The recommended way of installing Forest Admin is to run those commands locally, which will generate files in your current local directory.
However, you may require to install Forest Admin on a remote server: in this case, you must:
Edit the second command (lumber generate
):
change --application-host
to the URL of your remote server
Run those commands on that remote server instead of locally.
All remote environments must use HTTPS (port 443) for security reasons. Choosing to install this way will require that you set up SSL certificates on your server yourself.
Remember that the database credentials provided on the previous should reflect where the command will be run (i.e: the host and port might be different).
When you install Forest Admin, on the last step you are asked to run some commands:
The recommended way of installing Forest Admin is to run those commands locally, which will generate files in your current local directory.
However, you may require to install Forest Admin on a remote server: in this case, you must:
Edit the first command (docker run
):
change APPLICATION_HOST
to the URL of your remote server
Run those commands on that remote server instead of locally.
All remote environments must use HTTPS (port 443) for security reasons. Choosing to install this way will require that you set up SSL certificates on your server yourself.
Remember that the database credentials provided on the previous should reflect where the command will be run (i.e: the host and port might be different).