The melm Wiki

User Tools

Site Tools

Trace:
forgejo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
forgejo [2025/03/28 07:55] – [Set up Forgerunner:] ryanforgejo [2025/03/28 08:03] (current) – [Set up Forgerunner:] ryan
Line 5: Line 5:
 ====Set up Forgerunner:==== ====Set up Forgerunner:====
  
-- make a new directory and create a compose.yml file with the following: +- Copy and paste the following commands (Note: If using docker, change the podman commands and the socket to their docker equivalent):
-  services: +
-    forgejo-runner: +
-      hostname: forgerunner +
-      image: code.forgejo.org/forgejo/runner:5.0.4 +
-      container_name: forgejorunner +
-      environment: +
-        DOCKER_HOST: unix:///var/run/podman/podman.sock +
-      user: 0:0 #Gives permission errors if not root. Can this be fixed somehow? +
-      volumes: +
-        - ./data:/data +
-        - /var/run/podman/podman.sock:/var/run/podman/podman.sock +
-      restart: unless-stopped +
-       +
-      command: forgejo-runner -c /data/config.yaml daemon +
-- save it and create a new folder in the same directory called "data"+
  
  
Line 49: Line 34:
  
 - Follow the prompts. Enter your forgejo url and runner token from YourRepo -> Settings -> Actions -> Runners -> Create new runner - Follow the prompts. Enter your forgejo url and runner token from YourRepo -> Settings -> Actions -> Runners -> Create new runner
 +
 +- Check the runners list in your repository. It should show up as inactive.
  
 - Navigate to your repo either in browser or locally and create a new file under .forgejo/workflows/ called "deploy.yml" (or name it whatever you prefer) - Navigate to your repo either in browser or locally and create a new file under .forgejo/workflows/ called "deploy.yml" (or name it whatever you prefer)
Line 80: Line 67:
 Make sure to create matching secrets or adjust the variables accordingly. Make sure to create matching secrets or adjust the variables accordingly.
  
-- Testing required: by commenting out the line "on: [push]" and un-commenting the lines beneath it, it should be possible to specify which branch is being pulled.+- Testing required: by commenting out the line "on: [push]" and un-commenting the lines beneath it, it should be possible to specify which branch is being checked for updates.
  
 - Under "script: |" is the command line script that is run once an SSH connection is established. The SCRIPT secret contains the git pull command to update the repository locally. You can enter your credentials with this command by using the following syntax at the command line, replacing the capitalized words to whatever you need: - Under "script: |" is the command line script that is run once an SSH connection is established. The SCRIPT secret contains the git pull command to update the repository locally. You can enter your credentials with this command by using the following syntax at the command line, replacing the capitalized words to whatever you need:
   git pull https://USER:PASSWORD@forge.melm.xyz/USERNAME/REPONAME   git pull https://USER:PASSWORD@forge.melm.xyz/USERNAME/REPONAME
      
 +Make sure your local repository is synced by pulling or pushing the changes. Now the script should automatically run on every push.
forgejo.1743148559.txt.gz · Last modified: by ryan