Where Does LinkAce Store Links and Data?
LinkAce reads .env beside compose and persists MySQL plus storage volumes. Back up env, DB dump, and storage together.
Last updated
LinkAce follows the Laravel docker pattern. The .env file in the deploy folder carries app key, database credentials, and mail. MySQL holds links and users in a named volume, while a storage volume keeps thumbnails and exports.
Cron inside the stack handles link checks and dead detection. Those jobs read the same env, so a bad key breaks background checks first. Keep .env out of version control like any Laravel app. Queue workers for link checks share the database credentials from the same file.
Where LinkAce stores this, by platform
/opt/linkace/.env
App key, DB creds, and mail for the stack. Copy from the example file and set a real app key before first boot.
/var/lib/docker/volumes/linkace_db/_data
MySQL data with links, tags, and users. Dump with mysqldump rather than copying raw volume files across versions.
/opt/linkace/storage
Thumbnails, exports, and file attachments. Archive alongside DB dumps for full restores.
Frequently asked questions
How do I back up LinkAce?
Dump MySQL and archive the storage folder with .env beside both. Links, lists, and API keys restore as one unit from that set.
Where does LinkAce config live?
Copy .env.example to .env in the deploy folder and fill in DB passwords, mail, and app key. The compose file reads it for every service.
Notice an outdated path? Let us know.