Check the deployment is ready
The console's Readiness list and the matching server command, which say whether every required piece of a new deployment is in place.
- For
- Administrators
- Applies to
- Billet 1.0
- Updated
In the console
Open Deployment and look at Readiness at the top. When everything is in place it reads This deployment is finished. Otherwise each requirement is listed with its state, what was found, and how to fix it.
A command in the Fix column runs on the portal server. Most also have a control in the console; the commands are for when the console is what is missing.
On the server
The same check, without a browser. It changes nothing, and exits with an error when something is missing, so it is safe to run after every upgrade or from monitoring:
sudo billet-portal-task task setup -e production check:true(billet-portal-task is the helper from Install the portal.)
What it checks
| Requirement | Ready when |
|---|---|
| Certificate authority | It exists and is usable. See Create the certificate authority. |
| System operator | A system administrator exists other than the first-run account, or the first-run account's password has been changed. See Sign in for the first time. |
BILLET_SESSION_SECRET |
Set in /etc/billet/portal.env, and not a built-in development value. |
BILLET_BROKER_SECRET |
Set in /etc/billet/portal.env, and not a built-in development value. |
A deployment can also need things this list cannot see, such as DNS, certificates and the relay. Finish with a real connection: test a connection to a desktop, then sign in as an ordinary person and connect from the Billet app.