blob: 3435c203f2dab80d863e5de0e8b7c357b0fa5c0f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
---
slug: forgejo-setup-notes
title: "Forgejo Setup Notes"
date: "2026-03-09T03:15:27-04:00"
draft: true
---
A month ago I installed [Forgejo][]. I've been using it to develop a
couple of projects.
TODO:
- server setup
- apache configuration
- systemd service
- container
- runner setup
- rootless podman w/ dedicated `runner` user
- rootless podman runners on odroid n2l w/armbian, pi5, and
debian
- note about podman socket and enable-linger
- systemd service (plus config override)
- custom config to enable host networking
- armbian: install nft (check `pi.txt`)
- labels. note about ubuntu-act
pros:
- Great UI. Very similar to [GitLab][]
- almost everything I care about: issues, PRs, kanban,
projects, organization, MFA,
- easier to install and upgrade than [gitlab][]
- faster and less resource-intensive than [gitlab][]
- forgejo actions syntax is very similar to github actions
- used by codeberg.org
- plays nice with podman and rootless podman
cons:
- no gists
- finicky runner setup
- instructions are good, but there are gaps
- minor differences in action syntax but they pop up
- some actions only support older versions relative to
github
other:
- see gist for notes about forgejo, and podman command
- runner running in rootless podman as runner user
- note about podman socket and enable-linger
- systemd service (plus config override)
- custom config to enable host networking
- armbian: install nft
- ubuntu-latest label (use ubuntu-act)
- TODO: see notes/{pi,k3,x1}.txt
- TODO: actions/cache <https://code.forgejo.org/actions/cache>
- runner multi-connect:
<https://forgejo.org/2026-02-monthly-report/#forgejo-runner-v1270>
|
