switch to use faasd

Signed-off-by: Matti R <[email protected]>

Author: techknowlogick

_posts/2021-01-31-gitea-faas.md

@@ -1,5 +1,5 @@
 ---
-title: "Gitea automation using OpenFaaS"
+title: "Extend and automate self-hosted Gitea with functions"
 description: "Switching to Gitea doesn’t mean having to give up your bot automations"
 date: 2021-01-31
 image: /images/2021-01-gitea/gitea-sticker-header.jpg
@@ -23,46 +23,113 @@ In this post we will walk through building a simple bot to label pull-requests.
 
 ## Pre-requisites
 
-For the purposes of this guide we'll use a local install of Kubernetes, but any Kubernetes cluster could be used. The tutorial should take you less than 15-30 minutes to try.
+For the purposes of this guide we'll create a local virtual machine and install faasd on it, but these instructions can be extended to use a Digital Ocean Droplet, or even a Raspberry Pi. The tutorial should take you less than 15-30 minutes to try.
 
-A quick way to install all the tools you need is to use the [arkade](https://get-arkade.dev) cli tool.
+### Create a Virtual Machine and install faasd
+
+[Multipass](https://multipass.run) is a lightweight virtual machine runner, think docker-compose but for ubuntu virtual machines. We'll use this to get a virtual machine with faasd up and running quickly.
 
 ```bash
-# Get arkade, and move it to $PATH
-curl -sLS https://dl.get-arkade.dev | sh
-sudo mv arkade /usr/local/bin/
+# Install multipass
+## On macOS you can install multipass with the brew command
+brew install multipass
+## or, on Linux, you can install using the snap command
+snap install multipass
 
-# Run Kubernetes locally
-arkade get kind
+# Get VM Bootstrap instructions
+wget https://raw.githubusercontent.com/openfaas/faasd/master/cloud-config.txt
 
-# OpenFaaS CLI
-arkade get faas-cli
+# Generate a key for SSH-ing into your VM
+ssh-keygen -t rsa -b 4096 -C "faasd" -f $PWD/faasd_ssh
 
-# Create a cluster
-kind create cluster
+# Add your local key to the cloud-init file
+awk "NR==4 {\$0=\"  - $(cat faasd_ssh.pub)\"} { print }" cloud-config.txt > tmp
+mv tmp cloud-config.txt
 
-# Install OpenFaaS
-arkade install openfaas
+# Run a local VM
+multipass launch \
+  --cloud-init cloud-config.txt \
+  --name faasd
 
-# Install Gitea
-arkade install gitea
+# Verify your VM has been started
+multipass info faasd
 ```
 
-Next, you'll need to portforward both Gitea, and OpenFaaS, as well as login into the OpenFaaS gateway with faas-cli
+### Connect faas-cli to your faasd install
+
+Now that faasd is up and running, we'll need to login into the gateway with the `faas-cli`.
 
 ```bash
-# Forward the OpenFaaS gateway to your machine
-kubectl rollout status -n openfaas deploy/gateway
-kubectl port-forward -n openfaas svc/gateway 8080:8080 &
+# Install faas-cli on your host machine
+curl -sSLf https://cli.openfaas.com | sh
+
+# Get IP
+export VM_IP=$(multipass info faasd | grep IPv4 | awk '{print $2}')
+echo "Your IP is: $VM_IP"
+
+# Login into the faasd gateway
+export FAAS_PASSWORD=$(multipass exec faasd sudo cat /var/lib/faasd/secrets/basic-auth-password)
+export OPENFAAS_URL="http://$VM_IP:8080"
+echo $FAAS_PASSWORD | faas-cli login --password-stdin
 
-# If basic auth is enabled, you can now log into your gateway:
-PASSWORD=$(kubectl get secret -n openfaas basic-auth -o jsonpath="{.data.basic-auth-password}" | base64 --decode; echo)
-echo -n $PASSWORD | faas-cli login --username admin --password-stdin
+# Test that faas-cli connects to gateway
+faas-cli list
+```
+
+### Install Gitea on your Virtual Machine
 
-# Forward the Gitea application to your machine
-kubectl -n default port-forward svc/gitea-http 3000:3000 &
+Next we'll need to install Gitea it up and running. This example uses the bleeding edge nightly version, but for production use you may wish to use the current stable version of Gitea.
+
+```bash
+# SSH into your VM
+ssh -i ./faasd_ssh ubuntu@$VM_IP
+
+# Download Gitea nightly version
+wget https://dl.gitea.io/gitea/master/gitea-master-linux-amd64
+mv gitea-master-linux-amd64 gitea
+chmod +x gitea
+
+# Create base Gitea configuration
+cat >/home/ubuntu/app.ini <<EOL
+RUN_USER = ubuntu
+[server]
+DOMAIN = $(hostname -I | awk '{print$1}')
+DISABLE_SSH=true
+[database]
+DB_TYPE = sqlite3
+PATH = /home/ubuntu/gitea.db
+[security]
+INSTALL_LOCK = true
+[oauth2]
+ENABLE=false
+EOL
+
+# Create Gitea database
+./gitea --config $(pwd)/app.ini migrate
+
+# Create a Gitea user
+export GITEA_PASSWORD="TEMPOPENFAASPASSWORD"
+./gitea --config $(pwd)/app.ini admin user create --admin --name gitea_admin --password $GITEA_PASSWORD --email [email protected]
+
+# Run Gitea
+screen -d -m ./gitea --config $(pwd)/app.ini web
+
+# Exit out of the SSH connection
+exit
 ```
 
+### Sign into Gitea and create test repo
+
+Finally after Gitea is installed, we'll need to verify the installation. To do this we will open up the Gitea interface in the browser and login into it.
+
+In the install step we created an admin user with the username `gitea_admin` and password `TEMPOPENFAASPASSWORD`, we will take those and go to the login page at http://$VM_IP:3000/user/login
+
+![gitea login page screenshot](/images/2021-01-gitea/gitea_login_screenshot.png)
+
+Once logged in, we will create a git repository so when we need to add webhooks to it later it will be ready. In the top navigation bar we can select the `+` dropdown, and click the "New Repository" link. When we get to the new repository page we will name the repo `test_repo` and check the "Initialize Repository" option, just to have an example repository for testing purposes.
+
+![screenshot to create a repository in gitea](/images/2021-01-gitea/create_repo_screenshot.png)
+
 ## Build and deploy the Gitea bot function
 
 For this guide we will be using golang for the Gitea bot, but you can use any language that you are comfortable working with.
@@ -256,28 +323,26 @@ With the function now built, now it is time to deploy the function. First you'll
       GO111MODULE: on
     secrets:
       - webhook-secret # random string generated by you
-      - gitea-host # host of your gitea instance, ex. https://gitea.example.com/
-      - gitea-token # gitea api token generated from https://gitea.example.com/user/settings/applications
+      - gitea-host # host of your gitea instance, ex. http://$VM_IP:3000/
+      - gitea-token # gitea api token generated from http://$VM_IP:3000/user/settings/applications
 ```
 
 ```bash
 faas-cli secret create webhook-secret --from-literal "abc123"
-faas-cli secret create gitea-host --from-literal "http://gitea-http.default.svc.cluster.local:3000/"
+faas-cli secret create gitea-host --from-literal "http://$VM_IP:3000/" # Use IP from setup
 faas-cli secret create gitea-token --from-literal "GET FROM GITEA GUI"
 
 faas-cli up -f lgtmbot.yml
 
 ```
 
-Finally, we need to configure the repo in Gitea that you would like to manage with this function. This can be done by going to the webhooks settings of the repo (ex https://gitea.example.com/org/repo/settings/hooks), and creating a new Gitea webhook with the secret being the one you set above.
+Finally, we need to configure the repo in Gitea that you would like to manage with this function. This can be done by going to the webhooks settings of the repo (ex http://$VM_IP:3000/gitea_admin/test_repo/settings/hooks), and creating a new Gitea webhook with the secret being the one you set above.
 
 ![setup webhook in gitea](/images/2021-01-gitea/setup_gitea_webhook.png)
 
 ## Wrapping Up
 
-Now that we’ve seen how to create a simple bot using OpenFaaS, from here we can build upon this base and make more complex actions. The next step could be transforming the [lockbot](https://www.openfaas.com/blog/schedule-your-functions/) from an earlier post to support Gitea as well, or even extending [Derek](https://github.com/alexellis/derek/) to support Gitea. The possibilities are endless. Eventually we could end up with a number of functions to rival the GitHub apps marketplace.
-
-This post uses OpenFaaS, but you could use faasd to keep the installation requirements a minimum.
+Now that we’ve seen how to create a simple bot using faasd, from here we can build upon this base and make more complex actions. The next step could be transforming the [lockbot](https://www.openfaas.com/blog/schedule-your-functions/) from an earlier post to support Gitea as well, or even extending [Derek](https://github.com/alexellis/derek/) to support Gitea. The possibilities are endless. Eventually we could end up with a number of functions to rival the GitHub apps marketplace.
 
 ### Taking it further