Lup Yuen Lee 李立源 @lupyuen@qoto.org

I also installed several private instances of #Forgejo, including one for my own needs, looks promising, but at current time, their runner (needed for CI/CD), that I still need to setup, is marked as "alpha release, should not be considered secure enough to deploy in production". For information and found some other interesting related documentation, Forgejo is a fork by Codeberg.org of #Gitea that is itself a fork of #GOGS.

Already installed some #Gilab instances+runners, some Gitea/Forgejo servers without runners, need to learn its whole setup (runners+act+) and how to make test recipes, only tried some made by other ones on opensource project. Learnt and tested the basis of LXC deployment/management last week on #ArchLinux. Still few problems about IPv4 assignment in cross-architecture deployment (maybe a LXC-net bug?), IPv6 and lxc-attach for direct,local connexion to container works fine. #LXC would be far lighter than docker for tests.

LXC already has some #RISCV and #ARM pre-made templates image in default repository that works well in x86_64 server environment, that's probably not a big work to create and add new "templates". Forgejo can support LXC containers.

$ /usr/share/lxc/templates/lxc-download -l | grep riscv
alpine 3.20 riscv64 default 20250107_13:00
alpine 3.21 riscv64 default 20250107_13:00
alpine edge riscv64 default 20250107_13:03
debian trixie riscv64 default 20250108_05:24
ubuntu focal riscv64 default 20250108_09:58
ubuntu jammy riscv64 default 20250108_08:42
ubuntu noble riscv64 default 20250108_07:42
ubuntu oracular riscv64 default 20250108_08:18

@lupyuen I think I already saw it, but it's an amazing paper worth sharing.