To use this in a ci file, do the following
VERSION='v1.0.1' # Get the latest tagged version
tar xvf <(curl -sL https://github.com/ReeceM/koyeb-touch/releases/download/$VERSION/koyeb-touch-$VERSION-linux-amd64.tar.gz)
chmod x koyeb-touch
./koyeb-touch $KOYEB_API_TOKEN $KOYEB_APP_NAME $KOYEB_SERVICE_NAMEFor GitLab it can be something like so:
You need to add the following to your CI/CD pipeline settings as variables:
KOYEB_API_TOKEN |
KOYEB_APP_NAME |
KOYEB_SERVICE_NAME |
KOYEB_TOUCH_VERSION |
|---|---|---|---|
| This is the API token created in Koyeb | The name of the app, you can get it in the URL or what you called it | The name of the service, usually main |
This is the version of this binary package |
I would suggest placing the version of the binary in the variables section, as this allows you to update it without having to touch the CI/CD file
Below is an example of the Gitlab CI/CD file (it should also work in GitHub, haven't tested it though)
This is for Linux build images in the yml file, change the version requested by viewing
# This is a job process that will deploy to Koyeb forcing it to update the image and re-deploy
koyeb:
stage: deploy
allow_failure: true
script:
- apk add --no-cache libc6-compat
- wget -c "https://github.com/ReeceM/koyeb-touch/releases/download/$KOYEB_TOUCH_VERSION/koyeb-touch-$KOYEB_TOUCH_VERSION-linux-amd64.tar.gz" -O - | tar -xz -C .
- chmod x koyeb-touch
- ./koyeb-touch $KOYEB_API_TOKEN $KOYEB_APP_NAME $KOYEB_SERVICE_NAMEThis will then 'touch' the latest Koyeb service in your app and trigger a new deploy automatically.