Docker installer workflow and licensing flow done - docker container is working fine
This commit is contained in:
@@ -6,6 +6,8 @@
|
||||
2. One or more tenant accounts are attached to that registration.
|
||||
3. A time-bound license defines package, user, and installation limits.
|
||||
4. An activation key is generated, stored only as a BCrypt hash, and emailed.
|
||||
The recipient is always the primary contact email stored on the client
|
||||
registration; API callers cannot redirect the key to another address.
|
||||
5. The Technobee Service Installer blocks unless Docker, Docker Engine, and
|
||||
Compose v2 work.
|
||||
6. The installer validates the key, generates an RSA-3072 installation key, and
|
||||
@@ -44,6 +46,9 @@ All administration endpoints require an access token with
|
||||
3. `POST /api/v1/admin/tenants/{tenantId}/licenses`
|
||||
4. `POST /api/v1/admin/tenants/{tenantId}/licenses/{licenseId}/activation-key`
|
||||
|
||||
The activation-key request contains only `expiresAt`. The cloud service reads
|
||||
the delivery address from `client_registration_details.primary_contact_email`.
|
||||
|
||||
For replacements:
|
||||
|
||||
- `POST /api/v1/admin/tenants/{tenantId}/installations/{id}/decommission`
|
||||
@@ -71,6 +76,9 @@ compiled into the installer workflow.
|
||||
The installer asks for the Matrix or Cygnus Docker image and writes it to
|
||||
`.env` using the selected profile's image variable. After a successful run,
|
||||
review `compose.yml` and `.env`, then start with `docker compose up -d`.
|
||||
It also asks for the registry host, username, and password and performs
|
||||
`docker login --password-stdin`. The password is not stored in the generated
|
||||
installation package.
|
||||
|
||||
The installer asks for the output directory. Press Enter to accept the INI
|
||||
`output_directory`. It creates:
|
||||
|
||||
Reference in New Issue
Block a user