📈 Live Status: 🟩 All systems operational

This hosts the monitor and status page for Kuzzle, powered by Upptime.

URL	Status	History	Response Time	Uptime
Kuzzle Website	🟩 Up	kuzzle-website.yml	1312ms	100.00%
Kuzzle Blog	🟩 Up	kuzzle-blog.yml	263ms	100.00%
Kuzzle Docs	🟩 Up	kuzzle-docs.yml	250ms	100.00%
Discord #1	🟩 Up	discord-1.yml	457ms	100.00%
Discord #2	🟩 Up	discord-2.yml	491ms	100.00%
PaaS Console (API)	🟩 Up	paa-s-console-api.yml	461ms	100.00%
PaaS Console (Web)	🟩 Up	paa-s-console-web.yml	468ms	100.00%
PaaS Packages	🟩 Up	paa-s-packages.yml	470ms	100.00%
PaaS Container registry	🟩 Up	paa-s-container-registry.yml	488ms	100.00%
PaaS CD	🟩 Up	paa-s-cd.yml	480ms	100.00%
PaaS SSO	🟩 Up	paa-s-sso.yml	745ms	100.00%

Infrastructure

The hosting/ directory holds the Terraform files for deploying the status page infrastructure.

Installation

To work on the infrastructure, you will need to install several tools:

• just to have access to the pre-defined commands.
• Kourou to decrypt and encrypt the secret files.
• Terraform, either directly or using tfenv.
• The Scaleway CLI, then log in to your Scaleway account by creating an API key for yourself.
  Note: you'll need to select the "default" project as the project used for Object Storage operations.
• The GitHub CLI, then log in to your GitHub account.
• The AWS CLI, then log in to your AWS account using aws configure (the profile that will be used is default).

Preparation

If this is your first time working with the infrastructure, you will need to first initialize the directory:

just init
kourou vault:decrypt gh_secrets.enc.json --vault-key '<VAULT_PASSWORD>'

Note

The Vault password can be found in the company password manager.

Applying changes

To preview your changes to the infrastructure:

just preview

To apply them:

just apply

If you changed a GitHub Actions secret, you'll need to re-encrypt the file before committing it:

kourou vault:encrypt gh_secrets.json --vault-key '<VAULT_PASSWORD>'

Miscellaneous

Exporting the keys

If you need to directly use the Terraform CLI, you can export the access and secret keys used to authenticate against the S3 backend:

eval `just export-keys`

License

• Code: MIT © Anand Chowdhary, supported by Pabio
• Data in the ./history directory: Open Database License