Provision forgejo on k8s with c4k

Find a file

Mirco e57e9dd0c4 Bump c4k-common version		2023-03-28 11:27:17 +02:00
doc	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
infrastructure/docker-backup	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
public	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
src	Add files again	2023-03-28 10:02:50 +02:00
.gitignore	initial	2022-06-07 17:37:21 +02:00
.gitlab-ci.yml	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
copy-and-build-dda-io.sh	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
LICENSE	initial	2022-06-07 17:37:21 +02:00
package.json	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
project.clj	Bump c4k-common version	2023-03-28 11:27:17 +02:00
README.md	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
shadow-cljs.edn	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
valid-auth.edn	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00
valid-config.edn	Change name from gitea to forgejo	2023-03-28 09:46:15 +02:00

convention 4 kubernetes: c4k-forgejo

Purpose

c4k-forgejo provides a k8s deployment file for forgejo containing:

Click on the image to try out live in your browser:

Your input will stay in your browser. No server interaction is required.

After having deployed the yaml-file generated by the c4k-forgejo module you need to complete the setup for forgejo:

Open the URL of your forgejo-server, and you will be shown a configuration page.
Adjust the settings according to your needs
Add the administrator's data (name, password and email) and submit the page.
The required database will be created and the forgejo setup will be completed.
The SSH-URL for a repo has the format: "ssh://git@domain:2222/[username]/[repo].git Example: "git clone ssh://git@repo.test.meissa.de:2222/myuser/c4k-forgejo.git"