Where is the vault located on linux?

[variable]

I installed the commander via pip, but struggle to find the location of the local vault to verify the access permissions.

[sk-keeper]

It is not clear what is the issue.
Commander is expected to be installed into a separate Python virtual environment.
pip packages including Commander are installed into the ${YOUR_VIRTUAL_ENVIRONMENT}/lib/pythonX.X/site-packages/ folder.

Commander does not support local storage for your vault.
All records and folders are stored in memory.

Commander stores locally only the configuration file config.json.
The default file location is $HOME/.keeper folder.

[variable]

Thanks we thought there would be a local cache of the secret entries saved on disk so we want to make sure correct folder permissions are set. But since it's only stored in memory then I suspect it gets cleaned up after process exits?

…

On Fri, 13 Jun 2025, 2:02 am Sergey Kolupaev, ***@***.***> wrote: *sk-keeper* left a comment (Keeper-Security/Commander#1492) <#1492 (comment)> It is not clear what is the issue. Commander is expected to be installed into a separate Python virtual environment. pip packages including Commander are installed into the ${YOUR_VIRTUAL_ENVIRONMENT}/lib/pythonX.X/site-packages/ folder. Commander does not support local storage for your vault. All records and folders are stored in memory. Commander stores locally only the configuration file config.json. The default file location is $HOME/.keeper folder. — Reply to this email directly, view it on GitHub <#1492 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEIIX6E4DKFKTABG6CTIB33DGCBDAVCNFSM6AAAAAB7DXYUJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNRWHEYTAOBUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sk-keeper]

Yes, vault data gets cleaned up when Commander exits