Create a Forgejo service
VSHNForgejo is currently in alpha. This means that the service is still under active development and may undergo significant changes. Users should be aware that there may be bugs, incomplete features, and potential instability. We appreciate your feedback and encourage you to report any issues you encounter. |
Apply the following object on your namespace, as specified by its YAML description.
apiVersion: vshn.appcat.vshn.io/v1
kind: VSHNForgejo
metadata:
name: forgejo-app1-prod (1)
namespace: mynamespace (2)
spec:
parameters:
service:
adminEmail: "admin@mydomain.com" (3)
fqdn:
- "forgejo.mydomain.com" (3)
version: "10.0.0" (4)
writeConnectionSecretToRef:
name: forgejo-creds (5)
1 | Instance name |
2 | The namespace where the object will be created |
3 | Your full qualified domain name |
4 | Forgejo version - Supported Versions |
5 | The name of the secret where the connection details will be stored, it must be unique per namespace |
To get more information about all available configuration options, please see the API Reference |
Inspect your new Forgejo service
$ oc get vshnforgejo.vshn.appcat.vshn.io
NAME SYNCED READY CONNECTION-SECRET AGE
forgejo-app1-prod True True forgejo-creds 4m23s
When you see True
in the READY column, it means the instance is provisioned but the pods might still be starting.
It may take some time for the instance to be available especially during the provisioning phase.
Find the connection details
The connection details are stored in a secret. You can retrieve them with the following command:
$ oc get secrets forgejo-creds -o yaml
The output of the command above is a secret specification with the following structure:
apiVersion: v1
kind: Secret
stringData:
FORGEJO_PASSWORD: a09gGvIF3cKDlD7K (1)
FORGEJO_URL: forgejo.mydomain.com (2)
FORGEJO_USERNAME: forgejo_admin (3)
metadata:
(...) # omitted for brevity
1 | Password for the Forgejo instance |
2 | URL to access the Forgejo instance |
3 | Username to access the Forgejo instance |