social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

488
active users

#gogs

0 posts0 participants0 posts today
Replied in thread

@simonmic It took 10y to get my friends off of #whatsapp and most are probably not keen on installing yet another messenger. But #simplex surely looks very intriguing.

Same with #radicle now that they've nailed the protocols. I've moved from #gogs / #gitea / #forgejo to plain ssh 2y ago, maintenance had become too much of a burden. It's been great for me but unsurprisingly collaboration has gone down to zero. Maybe this can provide some middle ground? Will definitely try it out this year

I've been using #bitbucket for 10 years and I don't feel great about the 1 GB limit suddenly set to the sum of all repositories.

While I could just rely on my beloved #Gogs local git server, I would prefer to move to #Github, but the lack of transparency/commitment over AI training on private repositories on the free plans worries me (github.com/orgs/community/disc).

Any suggestions (beside paying, I know I know, but I'd rather not)? Just Gogs it is? toot.rainbow-100.com/objects/1

Replied in thread
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

Summary card of repository forgejo/runner
Forgejo: Beyond coding. We forge.runnerForgejo runner - alpha release, should not be considered secure enough to deploy in production

"Unfortunately, the maintainers did not implement fixes and stopped communicating with us at some point after initially accepting our report. All four vulnerabilities are still present in the latest release of Gogs (0.13.0) and the latest commit in the Gogs repository (5bdf91e at the time of writing)."

- Sonarsource vulnerability researchers

sonarsource.com/blog/securing-

#infosec#foss#gogs

🛎️ Heads up to Forgejo admins: The Forgejo security team discovered a critical security issue affecting #Forgejo, #Gitea and #Gogs. Check out forgejo.org/2023-11-release-v1 to learn more and immediately perform an upgrade, especially when you have untrusted users on your instance (i. e. open registration).

Codeberg users: Don't worry, our instance has already been patched in coordination with the Forgejo security team.

forgejo.orgForgejo Security Release 1.20.5-1
Replied in thread

@estevez I've used a self-hosted #Gogs > #Gitea > #Forgejo for years (for smaller and personal projects). It was great. But it became harder to maintain and more resource-hungry with all the new devopsy stuff (which I was hardly using anyway). Two months ago I gave up and switched to a plain ssh-hosted git setup with hooks for simple CI/CD, markdown and cgit as web frontend. Still very happy with it.

I just migrated the 50 odd repos from my #selfhosted #Forgejo instance used for small and personal projects and deleted it (which ran #Gitea and even #Gogs before).

The dev-ops push has made it too big, slow and difficult to maintain for me (new versions frequently breaking things). 90% of the projects only need issue tracking, pull requests and a wiki anyway.

I'll now try a barebones ssh-hosted setup with git hooks, #GitBug and #markdown files instead. #minimalism

Replied in thread

@twann @forgejo - As someone who would likely just be a consumer and not necessarily a contributor, I am not sure I fully understand why I would choose #forgejo over #gitea. Is it just due to how corporations tend to do bad things to open source projects? Are there any major goals of this soft fork that aren't in alignment with #gitea? I was also a #gogs user previously so I am interested in understanding the reasons but didn't fully grok the "why" for #forgejo

Je vais m'auto-heberger un serveur #git
Je teste donc #gogs qui a priori repond à mes besoins mais je me demande pourquoi #gitea est plus populaire que son père?
Je n'ai pas fait beaucoup de recherches mais visiblement la situation n'est pas tres saine pour gitea mais il ne faudrait pas que je mise sur le mauvais cheval.
Et pour #gitlab j'ecarte pour l'instant car fait beaucoup plus que mon besoin et consomme beaucoup de ressources. Ca reste un plan B quand même 😉