Bot Front Configuration Guide
The following table shows the environment variables required by each service. Be sure to make those available as arguments or in the manifest files of your deployment
Environment variable | Description | Required by |
---|---|---|
ROOT_URL | The Botfront app URL (e.g. https://botfront.your.domain) | botfront |
MONGO_URL | The mongoDB connection string (e.g. mongodb://user:pass@server:port/database ) | botfront botfront-api |
MONGO_OPLOG_URL | The mongoDB Oplog connection string | botfront (optional) |
MAIL_URL | An SMTP url if you want to use the password reset feature | botfront |
BF_PROJECT_ID | The Botfront project ID (typically my-first-project ) | rasa |
BF_URL | The botfront-api root url | rasa actions |
MODELS_LOCAL_PATH | Where the trained model returned by Rasa is stored locally. Defaults to /app/models/ and should not be changed in a containerized environment. The Botfront Dockerfile exposes a volume with that path | botfront (optional) |
Volumes
Although volumes are technically not required for Botfront to run and work, if you do not mount them your data will be gone when containers are destroyed.
Volume | Description | Used by |
---|---|---|
/app/models | Where Botfront stores the model retured by Rasa when the training is completed | botfront |
/app/models | Where Rasa loads a model from when it starts | rasa |
/data/db | Where MongoDB persists your data | mongo |
/app/actions | Where Action server stores custom actions | rasa-sdk |
/app/models
should be mounted on the same location so when Rasa restarts it can load the latest trained model.