update from sparkleup

This commit is contained in:
Madison Scott-Clary 2022-07-25 13:00:07 -07:00
parent b5a92c3c19
commit fb7c94454a
1 changed files with 18 additions and 2 deletions

View File

@ -22,12 +22,13 @@ To complete this tutorial, you will need the following:
* An Ubuntu 20.04 server configured with a non-root sudo user and firewall by following the [Ubuntu 20.04 initial server setup guide](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04).
* Docker installed. You can find out how to do this by following **Steps 1 and 2** of the [How to Install and Use Docker on Ubuntu 20.04](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04) tutuorial.
* Docker Compose installed. You can find out how to do this by following **Step 1** of the [How to Install and Use Docker Compose on 20.04](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-compose-on-ubuntu-20-04#step-1-installing-docker-compose) tutorial.
*
Once you have these steps complete, you can continue installing GoCD on your new server.
## Step 1 — Installing GoCD
There are several ways to install GoCD. As a Go binary, it is fine to run on its own, but this makes keeping the service up to date more difficult. You can also install it in a Docker container, which is a good way to keep the server containerized if you are running multiple applications on a single server.
There are several ways to install GoCD. As a Java binary, it is fine to run on its own, but this makes keeping the service up to date more difficult. You can also install it in a Docker container, which is a good way to keep the server containerized if you are running multiple applications on a single server.
For the purposes of this tutorial, however, we will be installing the service via the APT repository. This allows easier updates and lets the service run without the overhead of a Docker container.
@ -53,7 +54,7 @@ sudo apt install go-server
Every instance of GoCD needs at least one **agent**. Agents are the mechanism by which the server runs pipelines. They spin up an environment in which to execute the commands specified within the pipeline, and once they are finished running those commands, they clean up the environment.
As before, there are several different ways to install agents, each with their own benefits and drawbacks. For instance, installing with Docker will allow multiple agents to be running at a time and is suitable for multiple agents running at the same time. This may be preferable if you foresee running multiple pipelines concurrently. As before, you can also run agents through a Go binary downloaded from the GoCD website.
As before, there are several different ways to install agents, each with their own benefits and drawbacks. For instance, installing with Docker will allow multiple agents to be running at a time and is suitable for multiple agents running at the same time. This may be preferable if you foresee running multiple pipelines concurrently. As before, you can also run agents through a Java binary downloaded from the GoCD website.
Once again, you will be using an agent installed from the APT repository that you set up earlier in this step.
@ -63,6 +64,21 @@ sudo apt install go-agent
This will install the GoCD agent on the server and allow you to run at least one pipeline at a time.
### Setting Up Your Domain Name and HTTPS
In order to view the GoCD web interface, you will need a domain name pointed at your server as mentioned in the prerequisites. Once you have that DNS record properly in place, you will need to open the firewall ports to allow HTTP(S) connections:
```command
sudo ufw allow
edit a configuration file that the GoCD agent has installed in order to listen for requests on the proper address and ports.
Open the configuration file for editing. The following example uses `nano`. This file will contain environment variables that `go-server` relies on for its operation:
```command
nano /usr/share/go-server/wrapper-config/wrapper-properties.conf
```
## Step 2 — Hooking GoCD Up to Gitea
## Step 3 — Setting Up a Pipeline on GoCD