
Gitea supports internal TLS termination as well as redirection of http to https. That may be simpler than terminating in a reverse proxy. Let's try it. Also, make the dockerfile match the expectation of the job that there will be a gitea-init stage. Also, fix the repository root setting in app.ini. Change-Id: Ia6b66b53cebdb1afa49fef89a0559615f98052f1
15 lines
381 B
YAML
15 lines
381 B
YAML
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: gitea-app
|
|
namespace: gitea
|
|
type: Opaque
|
|
stringData:
|
|
secret_key: {{ gitea_secret_key }}
|
|
internal_token: {{ gitea_internal_token }}
|
|
lfs_jwt_secret: {{ gitea_lfs_jwt_secret }}
|
|
db_username: {{ gitea_db_username }}
|
|
db_password: {{ gitea_db_password }}
|
|
gitea_tls_cert: {{ gitea_tls_cert }}
|
|
gitea_tls_key: {{ gitea_tls_key }}
|