A guided walkthrough of the technical details to specify, understand, and acknowledge before signing up a new Tamanu deployment.
Pollen walks a BES team member and a prospective client through the technical decisions a deployment requires, surfaces the consequences of leaving the default supported path, and produces a permanent, shareable artifact that records the choices for the client's IT team, the BES technical team, and as a record of what was agreed.
It is public-facing and unauthenticated, and stores no client names, no free text, and no sensitive data, so the artifacts it produces are non-sensitive and addressable by an unguessable id alone.
The ruleset.ron file describes all the content of the form and the final report.
It is pulled from main by the live site every five minutes.
You can preview a ruleset change by pushing it to a branch in this repo and
appending ?config=name-of-branch to live URLs. Doing so with an in-progress
plan will fork that plan to a new version with the config being previewed.
Changing the engine or visual style requires code changes and a full deploy.
Run just watch-api and just watch-web in two terminals and open http://localhost:8090.