Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Forgejo Support #60

Open
heliophane opened this issue May 15, 2023 · 4 comments
Open

Add Forgejo Support #60

heliophane opened this issue May 15, 2023 · 4 comments
Labels
New Service Adds a new service to the playbook

Comments

@heliophane
Copy link

Forgejo is a fork of Gitea created by Codeberg that is designed to be a drop in replacement for Gitea.
https://forgejo.org/

@spantaleev
Copy link
Member

Using the Gitea role and overriding a few variables in your vars.yml file should work.

Most importantly, you should override the gitea_container_image variable: https://github.com/mother-of-all-self-hosting/ansible-role-gitea/blob/a75e575ecdec6a734e772b9df94d24dc54f1fb7f/defaults/main.yml#LL19C1-L19C112

Perhaps this way:

# Not strictly necessary to override these, but it prevents confusion
gitea_identifier: "{{ mash_playbook_service_identifier_prefix }}forgejo"
gitea_base_path: "{{ mash_playbook_base_path }}/{{ mash_playbook_service_base_directory_name_prefix }}forgejo"
gitea_config_database_name: forgejo
gitea_config_database_username: forgejo

gitea_container_image: codeberg.org/forgejo/forgejo:1.19.3-0

I haven't given it a try. If you do and this works well for you, we can document this on our gitea.md documentation page and possibly by creating a new forgego.md page which links to gitea.md#using-forgejo

At some point, it may make sense to fork the role, but for now it doesn't seem like there are any practical differences between Gitea and Forgejo and it doesn't seem like there's a good reason to go for Forgejo just yet (unless one has appeared and I don't know about it yet).

@moan0s moan0s added the New Service Adds a new service to the playbook label Jun 1, 2023
@jahanson
Copy link
Contributor

I wanted to get forgejo running with all of the mash backup addons but I ran into some permissions issues from a fresh install. Any recommendations?

Logs

image

My config

########################################################################
#                                                                      #
# gitea--forgejo                                                       #
#                                                                      #
########################################################################

gitea_enabled: true
gitea_hostname: git.hsn.dev
# Not strictly necessary to override these, but it prevents confusion
gitea_identifier: "{{ mash_playbook_service_identifier_prefix }}forgejo"
gitea_base_path: "{{ mash_playbook_base_path }}/{{ mash_playbook_service_base_directory_name_prefix }}forgejo"
gitea_config_database_name: forgejo
gitea_config_database_username: forgejo

gitea_container_image: codeberg.org/forgejo/forgejo:1.20.2-0

########################################################################
#                                                                      #
# /gitea--forgejo                                                      #
#                                                                      #
########################################################################

@jahanson
Copy link
Contributor

Turns out using the rootless package codeberg.org/forgejo/forgejo:1.20-rootless was the ticket. Works great so far.

@NeonMinnen
Copy link
Contributor

NeonMinnen commented Sep 6, 2023

Forgejo is a fork of Gitea created by Codeberg that is designed to be a drop in replacement for Gitea. https://forgejo.org/

Created a Forgejo role if you're interested. Attempting to merge upstream as we speak.

Forgejo has been officially added to the playbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Service Adds a new service to the playbook
Projects
None yet
Development

No branches or pull requests

5 participants