Self-hosted GitHub Action runners provide greater flexibility and control over your CI/CD pipeline. This guide will walk you through managing your self-hosted runner on a Linux server.

## **1. Setting Up the Self-Hosted Runner**

Before managing the runner, navigate to its installation directory. Typically, it is located in:

```bash
cd /var/www/html/[runner-name]
```

### **Installing the Runner as a Service**
To install the runner as a service, run:

```bash
sudo ./svc.sh install
```

### **Starting the Runner**
Once installed, start the service using:

```bash
sudo ./svc.sh start
```

---
## **2. Debugging and Managing the Runner**

### **Checking Runner Status**
To check if the self-hosted runner is active or has failed, run the following command inside the runner folder:

```bash
sudo ./svc.sh status
```

### **Restarting the Runner**
GitHub’s self-hosted runners do not have a direct restart command. Instead, you need to stop and start the service manually:

```bash
sudo ./svc.sh stop
```

Then, restart it with:

```bash
sudo ./svc.sh start
```

These steps ensure that your GitHub self-hosted runner remains operational and efficiently executes your workflows.

#Linux #Server

Self-hosted GitHub Action runners provide greater flexibility and control over your CI/CD pipeline. This guide will walk you through managing your self-hosted runner on a Linux server.

How to Control a Self-Hosted GitHub Action Runner