-
Notifications
You must be signed in to change notification settings - Fork 0
openhab Get Snapshot
Shell-scripts to update to a snapshot-build
If you are experimenting with the latest openHAB-snapshots, it can be quit annoying to download all nightly-packages, extract them, update all files and addons and copy/replace the configuration files, every time.
To automate this process there are two shell-scripts for Linux available.
the script openhab_get_snapshot.sh is a quick-and-dirty-script to download a new openHAB Snapshot to a new folder.
Usage is openhab_get_snapshot.sh nnn
, where nnn is the Snapshot-Number
Within the Script there is only one variable to set:
version is the actual Snapshot-Version (with a dash at the end) and has to be updated, if the Version number changes.
This is used to build the name of the subdirectory, to which openHAB will be downloaded.
If unchanged, the script will create a subdirectory under /srv/openhab/
with the name versionnnn (e.g. 1.3.0-461), then download all needed packages to another subdirectory zips/
, unzip the packages, move addons and link configurations/
, etc/
and webapps/images/
to /srv/openhab/
subdir
/
.
At the end, all that has to be done is to restart openHAB from the new path.
All addons will reside in runtime/addons_inactive if not moved automatically to runtime/addons/
from the script, so it is easy to activate more addons.
A assumption is, that all user-specific Stuff resides in /srv/openhab/configurations #the configs /srv/openhab/etc #for persistence-data /srv/openhab/images #images for the UI which makes it necessary to move or copy the data first (only once).
All delivered configurations/
are moved to configurations_old/
, just as etc/
is moved to etc_old/
and webapps/images/
is moved to webapps/images_old/
, so no data is lost (e.g. new openhab.cfg-entrys)
This script overwrites all files of the defined openhab-folder. The packages you want to update can be specified in the script. (see filelist, addonlist). You can also define file names to be excluded from the update process.
Installation
Community
- Support
- News Archive
- Presentations
- How to Contribute
- IDE Setup
- How to Implement a Binding
- How to Implement an Actions
- User Interfaces
- Classic UI
- iOS Client
- Android Client
- GreenT UI
- Bindings
- Asterisk Binding
- Bluetooth Binding
- Comfo Air Binding
- CUPS Binding
- digitalSTROM Binding
- DMX512 Binding
- EnOcean Binding
- Epson Projector Binding
- Exec Binding
- Fritz!Box Binding
- Fritz AHA Binding
- Homematic Binding
- HTTP Binding
- IHC / ELKO Binding
- KNX Binding
- Koubachi Binding
- MAX!Cube Binding
- MiLight Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- Network Health Binding
- Nibe Heatpump Binding
- Nikobus Binding
- Novelan/Luxtronic Heatpump Binding
- NTP Binding
- One-Wire Binding
- Onkyo AV Receiver Binding
- OpenSprinkler Binding
- OSGi Configuration Admin Binding
- Philips Hue Binding
- Piface Binding
- Pioneer-AVR-Binding
- Plugwise Binding
- PLCBus Binding
- Pulseaudio Binding
- RFXCOM Binding
- Samsung TV Binding
- Serial Binding
- Snmp Binding
- Squeezebox Binding
- System Info Binding
- Somfy URTSI II Binding
- Sonos Binding
- TCP/UDP Binding
- TinkerForge Binding
- VDR Binding
- Wake-on-LAN Binding
- Z-Wave Binding
- Persistence
- db4o Persistence
- rrd4j Persistence
- Sql Persistence
- Sen.Se Persistence
- Cosm Persistence
- Logging Persistence
- Exec Persistence
- Automation
- Scripts
- Rules
- Actions
- Misc
- REST-API
- Security
- Google Calendar Support
- Twitter Action
- Service Discovery
- Dropbox Bundle
- CometVisu
Samples
- Item definitions
- Sitemap definitions
- Binding configurations
- Rules
- REST Examples
- Tips & Tricks
- FAQ
- XSLT Transforms
- Scripts
- Integration with other applications
- Syntax highlighting for external editors
- Update-Scripts
- Samples-Comfo-Air-Binding
Release Notes