admin/changemaker.lite
1
0
Fork 0
Code Issues Packages Projects Releases 35 Wiki Activity

Rework Gitea init to use separate init container pattern

Browse Source 
The previous approach (custom CMD on gitea-app) failed because:
- Gitea's entrypoint generates app.ini as root, then drops to git user
- Overriding CMD ran our script before app.ini was generated
- su-exec to git user lost access to the entrypoint-generated config

Now uses the same pattern as nocodb-init: a separate container that
depends on gitea-app being healthy, shares the gitea-data volume
(which has app.ini), and runs gitea admin user create.

Bunker Admin
This commit is contained in:
bunker-admin
2026-04-09 13:25:56 -06:00
parent c5209887cc
commit c180bb5ace
3 changed files with 69 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files

72
scripts/gitea-init.sh
View File

@@ -1,62 +1,44 @@
#!/bin/sh
# =============================================================================
# Gitea Initialization Script
# Gitea Admin User Initialization
# =============================================================================
# Replaces the default CMD in the Gitea Docker container.
# Runs database migrations, creates the admin user (if credentials are provided
# and the user doesn't already exist), then starts the Gitea web server.
#
# The Gitea entrypoint (/usr/bin/entrypoint) has already:
# - Set up UID/GID, created directories, generated app.ini from GITEA__* env vars
# But it exec's our CMD still as root — Gitea refuses to run as root.
# We must drop to the 'git' user before running any gitea commands.
# Runs as a separate init container (like nocodb-init) AFTER gitea-app is healthy.
# Shares the gitea-data volume so the app.ini config is available.
# Creates the admin user if it doesn't exist, then exits.
# =============================================================================
set -e
PREFIX="[gitea-init]"
log() { echo "$PREFIX $1"; }
# Drop privileges: Gitea refuses to run as root. The Docker entrypoint
# sets up directories as root, then exec's the CMD (us) — still as root.
# Re-exec this script as the 'git' user via su-exec.
if [ "$(id -u)" = "0" ]; then
log "Dropping to git user..."
exec su-exec git "$0" "$@"
# The gitea binary needs app.ini to know the database connection.
# On the Gitea Docker image, GITEA_CUSTOM defaults to /data/gitea
# and app.ini lives at /data/gitea/conf/app.ini (created by gitea-app's entrypoint).
export GITEA_CUSTOM="${GITEA_CUSTOM:-/data/gitea}"
if [ ! -f "$GITEA_CUSTOM/conf/app.ini" ]; then
log "ERROR: No app.ini found at $GITEA_CUSTOM/conf/app.ini"
log "This means gitea-app hasn't completed its first startup yet."
exit 1
fi
# --- Step 1: Run database migrations ---
log "Running database migrations..."
MIGRATE_OK=false
for i in $(seq 1 10); do
if gitea migrate 2>&1; then
MIGRATE_OK=true
log "Migrations complete"
break
fi
log "Waiting for database... (attempt $i/10)"
sleep 3
done
log "Found app.ini at $GITEA_CUSTOM/conf/app.ini"
if [ "$MIGRATE_OK" = false ]; then
log "WARNING: Migrations may not have completed — starting anyway"
if [ -z "$GITEA_ADMIN_USER" ] || [ -z "$GITEA_ADMIN_PASSWORD" ] || [ -z "$GITEA_ADMIN_EMAIL" ]; then
log "No GITEA_ADMIN_USER/PASSWORD/EMAIL set — skipping"
exit 0
fi
# --- Step 2: Create admin user if credentials provided ---
if [ -n "$GITEA_ADMIN_USER" ] && [ -n "$GITEA_ADMIN_PASSWORD" ] && [ -n "$GITEA_ADMIN_EMAIL" ]; then
log "Creating admin user '${GITEA_ADMIN_USER}'..."
if gitea admin user create --admin \
--username "$GITEA_ADMIN_USER" \
--password "$GITEA_ADMIN_PASSWORD" \
--email "$GITEA_ADMIN_EMAIL" \
--must-change-password false 2>&1; then
log "Admin user created successfully"
else
log "Admin user already exists (or creation skipped)"
fi
# Create admin user (idempotent — returns non-zero if user exists)
log "Creating admin user '${GITEA_ADMIN_USER}' (${GITEA_ADMIN_EMAIL})..."
if gitea admin user create --admin \
--username "$GITEA_ADMIN_USER" \
--password "$GITEA_ADMIN_PASSWORD" \
--email "$GITEA_ADMIN_EMAIL" \
--must-change-password false 2>&1; then
log "Admin user created successfully"
else
log "No GITEA_ADMIN_USER/PASSWORD/EMAIL set — skipping admin creation"
log "Admin user already exists (or creation skipped)"
fi
# --- Step 3: Start Gitea web server ---
log "Starting Gitea web server..."
exec gitea web
log "Done"