Provision forgejo on k8s with c4k

Find a file

patdyn eb33cf5e0b [Skip-CI] Add Upgrade process for 1.19 to forgejo sem		2024-07-05 09:06:54 +02:00
doc	[Skip-CI] Add Upgrade process for 1.19 to forgejo sem	2024-07-05 09:06:54 +02:00
infrastructure	bump version to: 3.2.3-SNAPSHOT	2024-04-04 09:28:43 +02:00
public	Forgejo instead of gitea	2023-04-21 06:56:06 +00:00
src	bugfix	2024-04-04 09:27:42 +02:00
.gitignore	try to create native image	2024-02-16 16:27:04 +01:00
.gitlab-ci.yml	use newest ci-images	2024-02-19 16:16:54 +01:00
build-and-move-frontend.sh	Small adjustment and added development doc	2023-06-09 10:11:04 +02:00
build.py	fix arch	2024-02-21 16:21:08 +01:00
LICENSE	initial	2022-06-07 17:37:21 +02:00
package.json	bump version to: 3.2.3-SNAPSHOT	2024-04-04 09:28:43 +02:00
project.clj	bump version to: 3.2.3-SNAPSHOT	2024-04-04 09:28:43 +02:00
README.md	update doc	2024-02-20 18:33:04 +01:00
shadow-cljs.edn	use common wo reflection	2024-02-16 17:50:54 +01:00

convention 4 kubernetes: c4k-forgejo

Purpose

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

c4k-forgejo is an example how to create efficient k8s one shot deployments with https://repo.prod.meissa.de/meissa/c4k-common.

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"

Mirrors are: