Skip to content
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

Config not saved in /data/options.json #23

Closed
anthonyangel opened this issue Dec 21, 2017 · 3 comments
Closed

Config not saved in /data/options.json #23

anthonyangel opened this issue Dec 21, 2017 · 3 comments

Comments

@anthonyangel
Copy link

Where can I find the options.json file, my config isn't saved to /data/options.json (where the docs say that it should be), that file has my settings for the default ssh addon saved in it.

The settings persist on reboot, so must be saved somewhere, but I can't find them! I'd like to be able to store them under /config so that they can be kept in VCS with the rest of the config

@danimtb
Copy link
Owner

danimtb commented Dec 26, 2017

Hi @anthonyangel!

When you ssh into you pi you are seeing the filesystem of the ssh addon, not the dasshio one. That's why when you look at data/options.json you see the config of your ssh addon.

Unfortunately I think there is not a current default approach to save addons config under a VCS, AFAIK. However it coud be a good feature to add to Dasshio to let user choose where to store the options.

I will ask addon developers to look into this. Thanks!

@anthonyangel
Copy link
Author

Thanks for the explanation, that makes sense. I'll keep an eye out for anything about VCS integration for backups

@danimtb
Copy link
Owner

danimtb commented Feb 21, 2018

Closing this issue as there is no current official support for this and it is out of the scope for Dasshio. Feel free to reopen if you think it is needed!

@danimtb danimtb closed this as completed Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants