[RFC] Migrate forgeo to its own role

[DO1JLR]

Hello everyone.

As forgejo is becoming a hard fork of gitea, I'm proposing that it be moved to its own ansible role. (See forgejo news.)

What do you think about this?

I think future changes to the forgejo config could benefit from this. And since you can no longer swap the gitea binary with the forgejo binary, I don't see any advantage in keeping it in the same git project.

[adrinux]

Having just hit another problem with Forgejo installed via this role (issue#165) I can see some sense in this.

It would certainly be possible to add logic and documentation to work around these issues and differences, but it does complicate things and will presumably get more complex as time goes by.

On the one hand I prefer the simplicity of one role per project, on the other they are still very similar. I think for the most part this comes down to your personal preference as a maintainer and whether you will still be using both Gitea and Forgejo.

(Myself, I've switched to Forgejo and no longer use Gitea, I'd be happy to see Forgejo forked to it's own role.)

[TigerP]

I think it will be a good idea to fork this to a separate forgejo project.
I no longer use gitea and the current role works very well, but gives some confusion, because gitea is used for file/directory names in some places (/etc/gitea).

[adrinux]

So how does a fork need to happen @DO1JLR ?

Do you want a forgejo-only role that remains a part of the l3d.git collection, alongside a gitea only role and the forgejo runner role?
Do you even want the gitea only role to remain?

I suppose what I'm asking is are you going to do the fork and accept pull requests from us, or do I need to fork the project?

(I'm working on getting my own collection of roles ready for Debian 13 release and would like to get some work done on the fork ready for that.)

[DO1JLR]

I think in the near future I will create a fork of this role and embed it to the l3d.git collection as l3d.git.forgejo.