From 2ef95ab66b3e38e530e3e86543b6764337f7031b Mon Sep 17 00:00:00 2001 From: Josh Date: Fri, 9 Jan 2026 00:44:35 +0200 Subject: [PATCH] fix: resolve Woodpecker-Forgejo OAuth integration issues - Enable Forgejo registration for OAuth users (DISABLE_REGISTRATION=false) - Use public URL for Woodpecker OAuth redirects instead of internal hostname - Add WOODPECKER_OPEN=true to allow new user registrations - Bcrypt hash OAuth client secret before storing in database Co-Authored-By: Claude Opus 4.5 --- files/cloud-init/ops.yml | 6 +++++- files/stacks/docker-compose.ops.yml | 5 +++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/files/cloud-init/ops.yml b/files/cloud-init/ops.yml index ff354ca..f16c08a 100644 --- a/files/cloud-init/ops.yml +++ b/files/cloud-init/ops.yml @@ -9,6 +9,8 @@ packages: - git - curl - sqlite3 + - python3 + - python3-bcrypt users: - name: deploy @@ -63,12 +65,14 @@ write_files: sleep 10 + HASHED_SECRET=$$(python3 -c "import bcrypt; print(bcrypt.hashpw(b'$$WOODPECKER_FORGEJO_SECRET', bcrypt.gensalt()).decode())") + sqlite3 "$$DB" <