Installation automation - License key approach
This commit is contained in:
26
cygnus-installer/README.md
Normal file
26
cygnus-installer/README.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# Cygnus installation wizard
|
||||
|
||||
The wizard validates Docker, activates a client license, generates a unique
|
||||
3072-bit installation signing key, registers the installation, and writes the
|
||||
deployment files. The license key is never persisted.
|
||||
|
||||
```bash
|
||||
java -jar target/cygnus-installer-1.0.0-SNAPSHOT.jar
|
||||
```
|
||||
|
||||
Set `CYGNUS_CLOUD_URL` before execution. The wizard asks where deployment
|
||||
files should be written and offers `CYGNUS_INSTALL_OUTPUT` as the default.
|
||||
|
||||
The selected output directory contains:
|
||||
|
||||
```text
|
||||
compose.yml
|
||||
config/
|
||||
installation.yml
|
||||
keys/
|
||||
client-signing-private.pem
|
||||
client-signing-public.pem
|
||||
```
|
||||
|
||||
The private key is created with owner-only permissions on POSIX systems. The
|
||||
plaintext installation license key is never written to the output directory.
|
||||
Reference in New Issue
Block a user