-
-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat] store directory env var #85
Comments
Why would you need this? |
I want to make a snap package of it, but all the system-files lives in a read-only mount and I will need to specify where the store directory, that needs to be in a writable mount, is located. It's common to be able to set "config directories" through a flag or something?At the moment it will try to write to this directory in the r/o space, and fail. On Dec 18, 2020 7:32 AM, Daniel Lando <[email protected]> wrote:
Why would you need this?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
|
@jmgiaever You could create a symlink ? |
No, the path to the writable directory is changed for every revision of the snap, and the symlink will break. The symlink must also be created after installation to determine the writable location, and then the filesystem is readable and not possible to add a symlink to. On Dec 18, 2020 10:50 AM, Daniel Lando <[email protected]> wrote:
@jmgiaever You could create a symlink ?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
|
@jmgiaever I could make it configurable using env vars. Would it be ok for you? |
That would be perfectly fine :D Highly appreciated! :) |
@jmgiaever Sorry for the delay in this, there is an open PR ready :) |
) * feat: STORE_DIR env var and renamed OZW_NETWORK_KEY to NETWORK_KEY Fixes #85 * fix: utils * refactor: added jsdocs to utils * fix: removeSlash is not a function * fix: broken jsonStore tests * fix: lint errors * docs: env vars
Thank you! 👍 Appriciated! |
@robertsLando PS! The snap package is now live: https://community.home-assistant.io/t/zwavejs2mqtt-snap-package/278994 / https://snapcraft.io/zwavejs2mqtt |
Thanks @jmgiaever ! If you would like to add it to docs feel free to open a PR :) |
Thanks, I will. Just want to run it for some days, and fix the env.vars in the configuration script. I also read that zwavejs is pulling device configuration, so I need to find out a solution on how I can make that directory readable in this confined environment. Do you happen to know if this is the only file zwave-js is writing to? Maybe @AlCalzone knows? |
The configs come from |
Noted and fixed! Thanks :) |
How to change the path where the store-data is stored?
The text was updated successfully, but these errors were encountered: