You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The runtime creates a few files that have hardcoded paths in $OPENHAB_USERDATA. If these are backed up on one machine and restored on another then these paths may be incorrect.
If we can't change these to paths to references, we should store the paths in the backup folder so that the restore scripts can do a find and replace to the new path on those hardcoded files.
On Linux/Mac OS, I assume that the restore commands would looks similar to:
find ${OPENHAB_USERDATA}/config/ -type f -name "*.config" -exec sed -i'.bak' "s|${OLD_USERDATA}/|${OPENHAB_USERDATA}/|g" {} \;
find ${OPENHAB_USERDATA}/config/ -type f -name "*.config" -exec sed -i'.bak' "s|${OLD_RUNTIME}/|${OPENHAB_RUNTIME}/|g" {} \;
The runtime creates a few files that have hardcoded paths in $OPENHAB_USERDATA. If these are backed up on one machine and restored on another then these paths may be incorrect.
If we can't change these to paths to references, we should store the paths in the backup folder so that the restore scripts can do a find and replace to the new path on those hardcoded files.
On Linux/Mac OS, I assume that the restore commands would looks similar to:
This needed to be done (openhab/openhab-linuxpkg#181 (comment)) when the linuxpkg file paths moved from
**/openhab2/
to**/openhab/
:I will try to get a PR through if I get the time but don't think I'll be able to do something about the Windows script.
The text was updated successfully, but these errors were encountered: