PoolRotater Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Existing hosts: updates and support ======

This reference is for operators who already have an installation. New hosts should [[guides:hosting|contact Papapyrus for onboarding files]] first. Use the current instructions supplied for your installation; old version-pinned repair helpers are not general installers.

===== Updates =====

Keep the same installation, authorization, catalogs, titles, tuning, enrollment, ratings and statistics. Healthy opted-in hosts receive signed updates through their saved policy. Compatible worker updates wait for individual rooms to empty; shared-controller updates wait for all configured rooms on that host.

Use the installed release's protected operator entry and its exact instance. An entry from an older release may intentionally refuse after upgrade. The [[technical:operator_commands|operator command reference]] explains the available actions; these are machine-side commands, not player dot commands.

A temporary preparation refusal in a healthy room can defer and retry an update in current releases. A deliberately stopped host, uncertain ownership or a failed cleanup retains its separate checks. Publication does not force a stopped host to start. See [[wiki:room_updates|update windows and maintenance]].

===== If something goes wrong =====

Keep the installation state and reports, and contact Papapyrus. Send room links, times and timezone, the installed version, what players experienced and redacted support output. Include the safe failure code, failed operation and HTTP status when available.

Do not reinstall, delete journals or repeatedly start rooms to bypass an uncertain outcome. Recovery instructions must match the exact failure and release. A failed systemd unit and uncertain room ownership are different facts. The version-pinned packages in old release notes apply only to their documented states.

Never send passwords, OAuth credentials/codes, token files, bound invitations or raw backups. Keep unredacted evidence locally.

===== Sharing and privacy choices =====

Onboarding explains directory listing, public statistics, shared map ratings, diagnostics and update policy. Existing explicit opt-outs remain effective. Public directory listing does not publish passwords or private room rosters. Diagnostic reports are private maintainer records, separate from public player statistics.

For an existing host, ''network-reporting-configure'' accepts all four reporting choices through the current kit's protected standard-input schema. To disable all four:

<code json>
{"share_statistics":false,"consume_statistics":false,"operational_logs":false,"public_chat":false}
</code>

The choices can be configured separately, but ''public_chat'' requires ''operational_logs''. Use ''network-reporting-support'' to inspect pending changes. Leave the network agent running until a requested central withdrawal is acknowledged; an unavailable hub can delay that acknowledgment.

Ratings are separate: ''ratings-configure'' with ''{"share_ratings":false}'' disables contribution, and ''ratings-reader-configure'' with ''{"mode":"independent"}'' selects independent local feedback. Follow the current kit's full schema and invocation. Statistics consumption is bound when a worker starts, so a change can require its next safe replacement.

Historical player data is not automatically approved by enabling sharing. Reviewed public-room history follows its own installation-bound procedure. Local capture, hub acknowledgment, cache availability and website publication are separate stages.

===== Useful checks =====

  * ''status'' / ''support'' — installation, room and recovery summaries.
  * ''network-support'' — enrollment and heartbeat.
  * ''ratings-support'' — locally captured, queued and acknowledged feedback.
  * ''network-reporting-support'' — activity/diagnostic reporting.
  * ''update-status'' — discovery, waiting, installation or a held update.

Use ''ownership-review'' only under the stopped-service conditions required by your kit. Ask Papapyrus before attempting unfamiliar recovery operations.

[[guides:hosting|Hosting overview and contact]] · [[technical:operator_commands|Operator commands]] · [[wiki:stats_privacy|Privacy]] · [[updates:start|Release history]]