Based on the guide found at Forgejo Runner Setup

MacOS Instructions

1. Grab the binary for the runner
2. Put it at /usr/local/bin

Setting up Forgejo Runner as a launchd Daemon

To run the Forgejo Runner as a background service on macOS, you can use launchd.

1. Configure the forgejo-runner.plist file: The forgejo-runner.plist file needs to be configured with the correct paths. Use ~/.config/forgejo-runner for the runner's working directory and log files. The forgejo-runner.plist file in this directory has been updated to reflect this.

2. Create the configuration directory: This directory will store the runner's configuration and log files.

   mkdir -p ~/.config/forgejo-runner
   

3. Move the forgejo-runner.plist to LaunchAgents: The ~/Library/LaunchAgents/ directory is the standard location for user-specific launchd services.

   mv forgejo-runner.plist ~/Library/LaunchAgents/org.forgejo.runner.plist
   

4. Load the launchd service: This command registers the service with launchd.

   launchctl load ~/Library/LaunchAgents/org.forgejo.runner.plist
   

5. Start the launchd service: This command starts the runner service. Since RunAtLoad is set to true in the plist, it will also start automatically on login.

   launchctl start org.forgejo.runner
   

Managing the Forgejo Runner Service

Here are some useful commands to manage Forgejo Runner's launchd service:

• Check status:

  launchctl list | grep org.forgejo.runner
  

• Stop the service:

  launchctl stop org.forgejo.runner
  

• Start the service (if stopped):

  launchctl start org.forgejo.runner
  

• Unload the service (to prevent it from starting on login):

  launchctl unload ~/Library/LaunchAgents/org.forgejo.runner.plist
  

• Load the service (if unloaded):

  launchctl load ~/Library/LaunchAgents/org.forgejo.runner.plist
  

Logs for the runner can be found in ~/.config/forgejo-runner/launchd.log and ~/.config/forgejo-runner/launchd.error.log.