Développeur
External storage
Configuration of the optional external storage server for TradeJourney.
TradeJourney can use an external storage server as a temporary relay: the MT5 EA or NinjaTrader indicator deposits trades there, then TradeJourney retrieves them and imports them into its database. It is only a transit — data is not kept on this server. This configuration is entirely optional.
Start the storage server
The docker-compose.storage.yml file allows you to quickly deploy the service.
docker compose -f docker-compose.storage.yml up -d --build
Stop the service
docker compose -f docker-compose.storage.yml down
View logs
docker compose -f docker-compose.storage.yml logs -f
Environment variables
In your .env file:
STORAGE_SERVER_PORT=5000
STORAGE_SERVER_DEBUG=false
CLEANUP_DAYS_OLD=2
| Variable | Description |
|---|---|
STORAGE_SERVER_PORT | Storage server listening port |
STORAGE_SERVER_DEBUG | Enable debug mode (detailed logs) |
CLEANUP_DAYS_OLD | Age in days beyond which files are automatically deleted |
How it works
- Files are persisted in the Docker volume
storage_data. - A
storage-cleanupservice runs in a loop every hour to delete files older thanCLEANUP_DAYS_OLDdays. - API authentication is done via the
X-API-Tokenheader.
External storage is currently only used for MT5 EAs or NinjaTrader indicators to quickly retrieve the day's trades. For other import methods, it is not necessary.