Provision the event environment¶
Use this procedure when installing or reconciling the shared Forum and Pretix setup. Access to API credentials and production systems must be limited to authorized Community Team maintainers.
Prerequisites¶
- Access to the canonical
ansible-community/meetuprepository and itsuvenvironment. - Authorized Pretix and Forum API credentials configured as described in the tooling specification.
- A reviewed change for any city registry or environment configuration update.
Procedure¶
- Update the checkout and install locked dependencies with
uv sync. - Confirm the target Pretix URL and Forum API credentials point to the intended environment. Production RSVP is rsvp.ansible.com; tooling defaults to localhost for development.
- Run the read-only setup check from the repository root and resolve any
FAILresults:
The checker verifies organizer.teams:write through Pretix's permission-gated team-list endpoint. It lists other required Pretix write permissions by name as MANUAL, because verifying them would require a write request. Forum write access is also MANUAL. Plugin installation/configuration, Pretix bootstrap-user state, worker restart state, and live end-to-end behavior require operator verification. Discourse may omit a user's email from GET admin/users/{id}.json; an omitted email is reported as MANUAL, while an explicitly anonymized email remains a FAIL.
4. Run the environment provisioner from the repository root:
Provisioning reconciles named groups, invite links, and permissions. City invite links add new users to the matching meetup-attendee-{slug} group, allow up to 5,000 redemptions, and expire on 2030-01-01. Review the specification before changing access behavior.
The provisioner sets require_2fa=false on the Pretix staff and city organiser teams. Pretix-managed 2FA is not required; privileged SSO logins are protected by Forum 2FA through DiscourseConnect.