Difference between revisions of "Trigger"
From Fixme.ch
| Line 8: | Line 8: | ||
* It controls the LEDs over HTTP using | * It controls the LEDs over HTTP using | ||
* It's deployed in [[Kubernetes]], the image is built locally. | * It's deployed in [[Kubernetes]], the image is built locally. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== How to push changes == | == How to push changes == | ||
Revision as of 20:11, 22 February 2019
Information
git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api
- Trigger for the space status, also controls the LED_Retrofit
- It uses the twitter.pl and spaceapi.py scripts to retrieve the status and to change it, using javascript and XMLHttpRequest
- It controls the LEDs over HTTP using
- It's deployed in Kubernetes, the image is built locally.
How to push changes
$ ssh ubuntu@k8s.fixme.ch # Update the local repository cd led-ctrl-2018/ git pull # Build the docker image sudo docker build -t trigger . # Killthe pod and watch it come back kubectl delete --namespace ctrl pod/trigger-579d7dd765-krfvk kubectl get --namespace=ctrl pods
Archives
- It was deployed using a gitolite hook
- This was part of the Internal_Server
