Where Does Logto Store Config and Data?
Logto configures through environment with users and sessions in Postgres, plus connector files in packages.
Last updated
Logto keeps runtime settings in environment variables rather than a config file. Database URL, ports, and secrets arrive per deploy through the compose file or shell. Users and sessions persist as rows in Postgres.
Connector packages for social logins live in the codebase tree beside the core. Mount custom connectors as volumes in Docker setups. Back up environment files with a database dump for restores.
Where Logto stores this, by platform
[LogtoDir]/.env
Database URL, secrets, and ports for compose deploys live here. Users persist as rows in Postgres. Connectors mount as volumes.
Frequently asked questions
How do I back up Logto?
Copy the env file with a dump of the Postgres database. Connector customizations travel as volumes. Restore both sides onto matching versions.
Where is the Logto config file?
There is none by default. Environment variables carry every setting. Keep the env file out of git and version a template instead.
Notice an outdated path? Let us know.