Create your agent
const { createAgent } = require('@forestadmin/agent');
const agent = createAgent({
// Mandatory options (those will be provided during onboarding)
authSecret: process.env.FOREST_AUTH_SECRET,
envSecret: process.env.FOREST_ENV_SECRET,
isProduction: process.env.NODE_ENV === 'production',
// Optional variables
customizeErrorMessage: ...,
forestServerUrl: ...,
logger: ...,
loggerLevel: ...,
permissionsCacheDurationInSeconds: ...,
prefix: ...,
schemaPath: ...,
typingsMaxDepth: ...,
typingsPath: ...,
});
All mandatory variables are provided as environment variables during onboarding.
Your agent cannot be started without them, and no default values are provided.
This variable contains a random secret token which is used to sign authentication tokens used in request between your users and your agent.
It is generated during onboarding, but never leaves your browser, and is not saved on our side.
Never share it to anybody, as that would allow attackers to impersonate your users on your agent!
This variable contains a random secret token which is used to authenticate requests between your agent and our servers.
Unlike the
authSecret, it is stored in our database, so it can be privately shared with forest admin employees.Never share it publicly, as it would allow attackers to impersonate your agent with our servers. That would not cause any data leak, but opens the possibility for attackers to cause denial of service.
In development mode the agent has a few extra behaviors (when using
isProduction: false)- At startup, the agent will print the URL of all mounted charts
- When exceptions are thrown, a report will be printed to stdout.
When unexpected errors are raised in the agent code during a request, the error will be logged (using
options.logger), but in the admin-panel, the final user will get a default message 'Unexpected error'.This is done as to:
- Prevent error message from leaking internal information about the agent (credentials, ...).
- Prevent technical/cryptic error messages to show in the frontend.
This behavior can be customized.
createAgent({
// ...
customizeErrorMessage: error => {
if (error instanceof SequelizeConectionRefusedError) {
return 'Failed to connect to the database, contact John at 06 12 34 56 78 and tell him to reboot the server';
}
return 'Unexpected error, contact Jane at 06 87 65 43 21 and tell her to get it fixed.';
},
});
It allows to specify the URL at which Forest Admin servers can be reached.
createAgent({
// ...
forestServerUrl: 'https://api.forestadmin.com',
});
You may want to have control of the logger which is used by forest admin.
This configuration key allows to format and route logs to a logging service, instead of printing them in stdout.
createAgent({
// ...
loggerLevel: 'Info', // Valid values are 'Debug', 'Info', 'Warn' and 'Error'
logger: (logLevel, message) => {
console.error(logLevel, message);
},
});
Those permissions are enforced both in the frontend, and in your agent.
This configuration variable allows to customize how often the agent should ask the server to provide the permissions table.
createAgent({
// ...
permissionsCacheDurationInSeconds: 15 * 60,
});
This variable adds a prefix to the url at which routes are locally mounted on your application. It is mostly used for customers which wish to mount multiple agent instances on the same Node.js process (for setups using multiple forest admin projects).
Note that this variable has no influence on the base URL that will be used by your users to reach the agent: it is determined only by the application URL provided during onboarding and deployment.
Application URL during onboarding
This is done so that customers using reverse proxies can implement their routing table as they see fit.
Desired Local URLs | Desired Public URLs | How to configure your agent |
|---|---|---|
http://localhost:3000/forest | https://api.company.com/forest | prefix = ''
agentUrl = 'https://api.company.com' |
http://localhost:3000/forest | https://www.company.com/api/forest | prefix = ''
agentUrl = 'https://www.company.com/api' |
http://localhost:3000/prefix/forest | https://api.company.com/prefix/forest | prefix = 'prefix'
agentUrl = 'https://api.company.com/prefix' |
http://localhost:3000/local-prefix/forest | https://api.company.com/public-prefix/forest | prefix = 'local-prefix'
agentUrl = 'https://api.company.com/public-prefix' |
createAgent({
// ...
prefix: 'api',
});
This variable allows to choose where the
.forestadmin-schema.json file should be written in development, and read from in production.This allows to:
- Improve git repository organisation
- Work around read only folders (for instance, if developing using a read only docker volume).
- Have flexibility when using custom builds in production (code minification, ...)
createAgent({
// ...
schemaPath: '/volumes/fa-agent-configuration/schema.json',
});
import { createAgent } from '@forestadmin/agent';
import { Schema } from './typings';
createAgent<Schema>({
// ...
typingsPath: './typings.ts',
typingsMaxDepth: 5,
});
Last modified 5mo ago