4Seas
4Seas Systems PortalINTERNAL SYSTEMS PORTAL
OPERATION · 运维

The people and entries behind the systems.

How to maintain the 4Seas Bot, where the code lives, who is on call, and which systems are still waiting to be integrated.

Bot operations, code hosting, the on-call owner, and systems pending integration.

4Seas Bot — Operations

TELEGRAM BOT · @ZUCHIANGMAIBOT

🤖 4Seas Bot In production

Every evening at 19:00 (Asia/Bangkok) it tells the community what is on tomorrow; /ask answers from the community FAQ — and says "I don't know" when it doesn't.
Bot entry
t.me/zuchiangmaibot(@zuchiangmaibot)
Serving group
4Seas Community · 775 members — t.me/NomadsBase
Admin page
http://127.0.0.1:8477/ localhost only, password login (custom commands / runtime config / resend preview)
Remote access
ssh -N -L 8477:127.0.0.1:8477 user@host — the admin page binds loopback only, against DNS rebinding
Repository
github.com/4seas-community/4Seas-bot · local ~/Dev/tools/4Seas-bot
Auto-start
macOS deploy/com.4seas.bot.plist → LaunchAgents · Linux deploy/4seas-bot.service → systemd
Data source
Social Layer · app.sola.day/event/4seas — imported 08:30 / 18:30, preview posted 19:00; admins use /sync to import and /reload to reload
Watch out
A sleeping machine misses that night's preview and won't backfill (the admin page can resend); mind hibernation before 19:00 on laptops.
$cd ~/Dev/tools/4Seas-bot && ./start.sh --bg # start in background
$./start.sh --status # check status
$./start.sh --stop # stop (single-instance guard rejects a second one)
⚠️
Wrong is worse than silent: when data can't be read the bot stays silent and only alerts. After editing data/faq.md、data/keywords.yaml、data/commands/*.yaml run /reload to apply.

Infrastructure

INFRASTRUCTURE

🍵 tea.4seas.xyz Online

Self-hosted Gitea — 4Seas' private Git home.
tea.4seas.xyz
Address
tea.4seas.xyz
Use
Internal code hosting / mirroring; public mirrors live on GitHub · 4seas-community

☁️ Cloudflare

The publishing layer for every outward-facing system.
Pages projects
canteenos · idoris-office-suite · 4seas-homepage-preview
Domains
4seas.xyz (incl. path apps /coliving /event /residency) · tea.4seas.xyz
Subdomains
Not configured yet — systems are reached via pages.dev and 4seas.xyz paths for now.

On-call owner

ON-CALL OWNER
JH
Jiao Huifeng jhfnetboy · owner of the 4Seas Bot and every system

Pending integration

PENDING INTEGRATION
1

coliving Pending

The co-living marketing page on the main site. The beta system is live; this page awaits integration into the portal's navigation.

2

booking Pending

The booking system: the code lives in a private GitHub repo, with no public page yet (4seas.xyz/booking). It will connect to the Coliving PMS booking lifecycle — the top priority for portal integration.

3

event Pending

The events system: Social Layer holds the event data; the 4Seas Bot previews it nightly. The goal is one unified events entry.

4

residency Pending

The 4Seas Residency programs page — the outward entry for long-stay products, to be unified under the portal navigation.

🧭
Suggested order: booking first (private repo, no public page yet) → coliving page / event / residency (path apps into one navigation). Homepage is already an operating system. Once everything is ready, request 4seas.xyz subdomains and make the portal the single entry.