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

Provide folder USERDATA as well in \public\openHAB2\. #103

Closed
loovanloon opened this issue Oct 11, 2017 · 11 comments
Closed

Provide folder USERDATA as well in \public\openHAB2\. #103

loovanloon opened this issue Oct 11, 2017 · 11 comments

Comments

@loovanloon
Copy link

loovanloon commented Oct 11, 2017

ENHANCEMENT:
For backup and restore purposes of the installation configured through the paper UI I think it is usefull to provide access to the USERDATA folder as well in the \public\openHAB2\ folder


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@cniweb
Copy link
Member

cniweb commented Oct 11, 2017

The folder USERDATA should also be linked via
/public/openhab2/
or
/smarthome/openhab2/
or
/var/services/homes/openhab2/

@SchoppAx
Copy link
Collaborator

@cniweb tell me if I'm wrong, but i think the "innovation" of the openhab2 config files (userdata) are, that they can be full managed with the PaperUI. So the user doesn't need to change the config files itselfs.

@loovanloon
Copy link
Author

loovanloon commented Oct 12, 2017

@SchoppAx The issue is not changing the files, but backing up the files.

In OH2 there are indeed 2 ways of configuration:

  1. through config-text files: stored in /openhab2/conf/ (OH1 style)
  2. through PaperUI: stored in JSONDB in /openhab2/userdata/

Hence to (easily) backup the configuration that was made through the PaperUI (and stored in JSONDB) you also need easy access to /openhab2/userdata/

@aurelio1
Copy link

While the PaperUI can make several things easier, it is far from being that powerful to replace manual editing of config files. But the config files are already linked in the public folder so it is no issue at all editing them from DSM.
If you set up a new device, from my experience it happens often that you have to check the logfiles or changing some log settings (these are also in the userdata folder). I did the link myself, but for sure it would be useful if the SynOH2 installation linked the userdata folder to the public as it does with the config folder. And for backup also, as you write. It is useful anyway.

@cniweb
Copy link
Member

cniweb commented Oct 12, 2017

Another case would be the update. Because the update does not work, but only an uninstall and install. The data will be deleted.

cniweb referenced this issue Oct 22, 2017
Signed-off-by: Christian Häussler <[email protected]> (github: @cniweb)
@cniweb
Copy link
Member

cniweb commented Oct 22, 2017

@loovanloon and @aurelio1 I add the userdata folder, is this ok (see my commit)?

@aurelio1
Copy link

@cniweb Great, thank you! I just wondered why it is necessary to remove the single userdata subdirectories such as tmp, log, logs and cache. Why didn't you do it at once, as with the conf directory that includes all subdirectories? I did it manually up to now and moved the directory and linked to it in one operation.

@cniweb
Copy link
Member

cniweb commented Oct 22, 2017

@aurelio1 Because the directories:
config, etc, jsondb and kar
contain data that must be retained during the update.

@loovanloon
Copy link
Author

loovanloon commented Oct 28, 2017

@cniweb Christian, Where can I download the SPK that contains the change? I'm quite new to Github.

@cniweb
Copy link
Member

cniweb commented Oct 29, 2017

I think I have time this sunday...

@cniweb
Copy link
Member

cniweb commented Nov 1, 2017

@cniweb cniweb closed this as completed Nov 16, 2017
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

4 participants