Created attachment 239608 [details] www/forgejo This patch adds www/forgejo, a fork of www/gitea
This is surely needed, as we don't yet have this in order to migrate away from the predecessor. Waiting on this so migration to this drop in replacement can be completed.
This corresponds to the following issue at the projects forge, adding support for FreeBSD at the project level. https://codeberg.org/forgejo/forgejo/issues/230
A group that I'm a member of is experimenting with moving from Gitea to Forgeio. We are currently building Forgeio by applying this patch to the ports tree, and it appears to be working. The only thing we ran into is that the directories in the rc.d script are still "gitea", so we had to change that before it would start from eg. /var/db/gitea to /var/db/forgejo. I'm not sure what forgejo does by default, it may still be using gitea directories, but we renamed everything in our config file and if I change the two directories listed in the rc.d script this starts working.
Created attachment 239617 [details] forgejo.diff That must have missed my scan through, updated it here
Created attachment 240654 [details] v3 patch, fixes LOCALEs and minor tweaks Making BINDATA option be part of DEFAULT_OPTIONS worked for me, is that appropriate to resolve this error on first run: 2023/03/07 23:03:31 ...rvices/cron/tasks.go:200:RegisterTaskFatal() [F] [6407c2c3-41] Unable to register cron task update_mirrors Error: translation is missing for task "update_mirrors", please add translation for "admin.dashboard.update_mirrors" ok - poudriere 13.1-RELEASE amd64 ok, portlint/portclippy wanted minor tweaks before we commit this: - we can't ship a config file that has an existing JWT secret, internal token etc - it needs a pkg-message describing how to do a fresh install - and importantly, how to migrate from gitea -> forgejo - having /usr/local/share as an app-writable space feels wrong, should we put this in e.g. /va/db/forgejo or some other dir? I'm too new to feel comfortable doing these notes yet, can anybody help?
Created attachment 241569 [details] Patch to add the new port www/forgejo Hi, I gave it a try and updated to the latest forgejo release and added a small pkg-message. Also the hard coded secret values are removed from the sample config. Please review and leave comments. It would be great to have this in ports/packages. :-) Kind regards, Jens
Created attachment 241844 [details] www/forgejo: New port: Self-hosted lightweight software forge, www/gitea fork Updated to v1.19.2-0 :) What's left to get this merged? I think all concerns were addressed
ah (In reply to Dave Cottlehuber from comment #5) - and importantly, how to migrate from gitea -> forgejo The directories are configurable, so for the purpose of migration, all required is to swap out the config paths - the fork is a soft fork, rebased and kept in sync by version, it's a drop-in replacement :) - having /usr/local/share as an app-writable space feels wrong, should we put this in e.g. /va/db/forgejo or some other dir? GITEA_WORK_DIR refers to the working directory, not a directory used to do work, so nothing variable is going in /share, not to worry. There also already is content going in /var/db/forgejo
not going to get this done before vacation, returning to pool.
Is there anything still preventing this from getting merged? I'd like to migrate my gitea instance to forgejo as well.
2024 says "Hello, it's me!". What's the current state or preventing it from being merged? If there's something we can assist or boost it up to get merged, just let us know! Cheers, gyptazy
I'd suggest that somebody updates the patch to match the latest upstream release and marking the previous patches as obsolete accordingly.
Created attachment 247700 [details] Patch to create a new www/forgejo port. Here is a new patch with the latest version of forgejo. I couldn't obsolete all other patches though. :-| Kind regards, Jens
(In reply to Jens Grassel from comment #13) +1
Created attachment 248606 [details] Add forgejo port + update to latest 1.21.5 version Latest patch (100% thanks to the original authors, I'm only updated forgejo to latest version 1.21.5). Also, I'm tested it. Migrated from gitea on my own server, all works as expected. Build log from poudriere with this patch: https://poudriere.vovkasm.org/data/13-2-amd64-dev/2024-02-18_02h19m14s/logs/forgejo-1.21.5.0.log
Created attachment 248982 [details] Add forgejo port + update to latest v1.21.7 Refreshed patch (updated to latest v1.21.7) attached. Build log: https://poudriere.vovkasm.org/data/13-2-amd64-dev/2024-03-06_17h58m16s/logs/forgejo-1.21.6.0.log Also, it would be very good, if someone can pay attention to this port and merged it. Forgejo since 1.20 is a hard fork of gitea (https://forgejo.org/2024-02-forking-forward/#the-hard-forking-process), so migration can become be more troublesome in future.
Comment on attachment 240654 [details] v3 patch, fixes LOCALEs and minor tweaks Patchset with more recent versions have been submitted.
Comment on attachment 241844 [details] www/forgejo: New port: Self-hosted lightweight software forge, www/gitea fork Patchset with more recent versions have been submitted.
Comment on attachment 247700 [details] Patch to create a new www/forgejo port. Patchset with more recent versions have been submitted.
(In reply to Vladimir Timofeev from comment #16) Next time be a little bit attentive with the Commit Messages for git am formatted patches and also before submitting it. This time no action is required.
Committed at https://cgit.freebsd.org/ports/commit/?id=00770786d88e06602a7dd3ed9cf0b2c96da4527f But as usual I missed the PR with git formatted patches again.