Difference between revisions of "Trigger"
From Fixme.ch
(→How to push changes) |
|||
| Line 4: | Line 4: | ||
git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api | git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api | ||
| − | * Trigger for the space status, also controls the [[LED_Retrofit]] | + | * Trigger for the space status, also controls the [[LED_Retrofit]] https://trigger.fixme.ch |
* It uses the [https://github.com/fixme-lausanne/Twitter-Hackerspace-Status twitter.pl and spaceapi.py scripts] to retrieve the status and to change it, using javascript and XMLHttpRequest | * It uses the [https://github.com/fixme-lausanne/Twitter-Hackerspace-Status 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 controls the LEDs over HTTP using | ||
Revision as of 18:35, 11 February 2022
Information
git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api
- Trigger for the space status, also controls the LED_Retrofit https://trigger.fixme.ch
- 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 ~/ctrl 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
