newsfeed/asset/firewalld/newsfeed-api.xml at 243b17e9b3f04e66b53022aa4dae599fe0733955 - newsfeed - Gitea: Git with a cup of tea

grenade/newsfeed

Files

rob thijssen 81fe5f7d4d

deploy / build-web (push) Successful in 1m34s

Details

deploy / deploy-web (push) Successful in 4s

Details

deploy / build-api (push) Successful in 6m17s

Details

deploy / deploy-api (push) Successful in 10s

Details

fix: move newsfeed-api off 8081 to 22672 (conflict-unlikely port)

8081 is the alt-HTTP port — one of the crowded defaults every proxy/dev server
grabs — so it's collision-prone on a shared host. Move to 22672, a registered-
range port in the sparse 20000s band, derived deterministically from the
service name and recorded in architecture port-allocations.md.

Updated everywhere the number appears: api bind config + default, firewalld
service XML, nginx upstream, vite dev proxy, deploy workflow API_PORT,
infra-setup (SELinux semanage label), and docs.

Operator note: re-run script/infra-setup.sh on slartibartfast to relabel the
SELinux port (22672) and ship the updated firewalld XML before the next deploy
restarts the api on the new port.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP

2026-07-08 12:25:26 +03:00

8 lines

295 B

XML

Raw Blame History

 <?xml version="1.0" encoding="utf-8"?>
 <service>
   <short>newsfeed-api</short>
   <description>newsfeed REST/JSON API. Reached over the WireGuard mesh by the oolon edge
   proxy, which terminates TLS and reverse-proxies to this port.</description>
   <port protocol="tcp" port="22672"/>
 </service>