The core server providing the REST API and communication with various sensors and devices. Read more on the wiki.
Prereqs needed:
- vagrant, virtualbox
- java
git clone https://github.com/homeki/homekicore.gitcd homekicore./gradlew jarcd vagrantvagrant up./run-server.sh
This will start the jar built through gradle on a vm. To debug, add the debug argument to run-server.sh
(attach a remote debugger to port 5050). The API will be exposed on port 5000 when the jar is running.
To run the API test, an instance of Homeki need to be started in test mode. Test mode clears the database and performs some configuration changes to mock devices and such.
cd homekicorecd vagrantrun-test-server.sh(debugparameter works just as forrun-server.sh)cd .../gradlew build -DrunTests(or run them from inside your editor)
Releases are available in a Debian repository at http://repository.homeki.com. There are two "suites", unstable and stable. git push to develop updates the package in unstable, git push to master updates the package in stable.
The packages must be signed with the Homeki gpg key when they are uploaded to the
debian repo. To check if the gpg is present, use gpg --list-secret-keys, make sure
Homeki Development Team <contact@homeki.com> exists.
If it does not exist, use gpg --import <key>.asc to import it.
Install deb-s3 and upload debian package with:
deb-s3 upload --endpoint s3-eu-west-1.amazonaws.com --access-key-id <id> --secret-access-key <secret> --codename <stable|unstable> --sign <gpg_key_id> --bucket repository.homeki.com --origin homeki.com --suite <stable/unstable> --prefix packages <debfile>