You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.)
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.
The text was updated successfully, but these errors were encountered: