#2 Explore current Forgejo deployment methods
Closed by ryanlerch. Opened by humaton.

Upstream provides deployment configuration as Kubernetes helm chart.
Explore and evaluate the deployment and its suitability for our needs in staging Openshift clusters.

Information about helm deployments can be found in Opneshift documentation

Staging

:black_medium_square: create application in openshift cluster

Production

:black_medium_square: create application in openshift cluster


Metadata Update from @humaton:
- Issue assigned to dkirwan

From 2025-02-05 Matrix meeting paraphrased from David Kirwan's update: "Still working on it. Got pulled into other things. Hope to get back to this soon. Helm is intalled on os-control machines and read to be used for deployment".

Have a staging instance running on Openshift, installed via the upstream helm charts, currently looking at configuring with modifications to enable FAS auth and disabling registrations, then passing in the configuration as part of the installation or post installation configuration via ansible.

Deployment on the staging openshift cluster is deployed: https://forgejo.apps.ocp.stg.fedoraproject.org/

Has FAS auth configured, missing some config magic to auto register users, will keep looking into it until thats completed, but in the meantime somethings up and running for folks to poke.

We've figured out the auto registration issue, so now logging in via FAS should work correctly.

Looking at using the forked fedora helm charts next, and making the configuration changes we already know are needed regarding auth.

Steps required to create the OCI images of the forked helm charts now captured, will build and package the helm chart and attempt to deploy forgejo, including the customisations to date including FAS auth and user registration disabled, libravatar etc etc.

Ansible playbook/role can deploy a forgejo instance in staging on demand with all currently requested configurations.

Moved to https://codeberg.org/fedora/forgejo-deployment/issues/12

Metadata Update from @ryanlerch:
- Issue status updated to: Closed (was: Open)

Metadata