)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"19f5b3cdc00be27881a9c739110a04b19d013bfa","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dd5836a5_f3a2556a","updated":"2026-04-03 16:05:55.000000000","message":"I keep waffling between whether or not we should just try to use more https, but this passes testing and is similar to how many other services are configured so it is probably fine.\n\nOne thing I note is that we could potentially use https://localhost:3081 to do all of the gitea configuration. The downsides to that are that localhost isn\u0027t in our ssl certs (but we already knew that which is why we didn\u0027t validate certs previously) and it means that if apache is down we won\u0027t configure gitea. I think using http://localhost:3000 is fine since that speaks directly to gitea and is over the loopback. Minimizes the potential number of things that can go wrong.","commit_id":"3a0139934419d60d49dc0d3c65d5d3a03f750dcb"}],"playbooks/roles/gitea/templates/app.ini.j2":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"1d9d5d330844a1e4a1e12cf59218ac8acf8017f0","unresolved":true,"context_lines":[{"line_number":7,"context_line":"[server]"},{"line_number":8,"context_line":"APP_DATA_PATH \u003d /data/gitea"},{"line_number":9,"context_line":"SSH_DOMAIN \u003d localhost"},{"line_number":10,"context_line":"PROTOCOL \u003d http"},{"line_number":11,"context_line":"HTTP_PORT \u003d 3000"},{"line_number":12,"context_line":"ROOT_URL \u003d {{ gitea_root_url | default(\u0027https://opendev.org\u0027) }}/"},{"line_number":13,"context_line":"DISABLE_SSH \u003d false"}],"source_content_type":"text/x-jinja2","patch_set":3,"id":"29eb4e1d_595469df","line":10,"updated":"2026-04-07 21:02:30.000000000","message":"I\u0027m 95% certain that we won\u0027t restart Gitea to pick up the app.ini change, but we will restart Apache to pick up the vhost changes. That means when we go to production we will have mismatched configuration between apache and gitea and the service won\u0027t be reachable.\n\nI think the solution to this is to have the existing playbooks/roles/gitea/tasks/main.yaml tasks for stopping and starting gitea when container images change also check the case where app.ini has changed. If app.ini changes we should also stop then start gitea. That should keep things in sync well enough.\n\nThen if we want to be extra careful we can land this change with only one gitea backend not in the emergency file. Check that it applies cleanly and if so reenqueue the deploy buildset and update the others.","commit_id":"3a0139934419d60d49dc0d3c65d5d3a03f750dcb"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"7d843ef04c89ae61a2868e1a7d1cae9d3374fd02","unresolved":false,"context_lines":[{"line_number":7,"context_line":"[server]"},{"line_number":8,"context_line":"APP_DATA_PATH \u003d /data/gitea"},{"line_number":9,"context_line":"SSH_DOMAIN \u003d localhost"},{"line_number":10,"context_line":"PROTOCOL \u003d http"},{"line_number":11,"context_line":"HTTP_PORT \u003d 3000"},{"line_number":12,"context_line":"ROOT_URL \u003d {{ gitea_root_url | default(\u0027https://opendev.org\u0027) }}/"},{"line_number":13,"context_line":"DISABLE_SSH \u003d false"}],"source_content_type":"text/x-jinja2","patch_set":3,"id":"ca918836_8208729f","line":10,"in_reply_to":"29eb4e1d_595469df","updated":"2026-04-08 21:43:36.000000000","message":"Done","commit_id":"3a0139934419d60d49dc0d3c65d5d3a03f750dcb"}]}