Installation with existing database

This page covers the installation wizard steps for connecting SigningHub to an existing database. The wizard will guide you through selecting the correct deployment mode, skipping database creation, and pointing to the existing database instance. This flow is best suited when you are reusing an enterprise-managed database or restoring SigningHub from a backup.

---

Run Interactive Installation

Run the included script to launch the installation wizard. It will configure your environment, update settings, and start the required containers.

# Make script executable
chmod +x startup.sh

# Run interactive installation wizard
./startup.sh

# To run the installation wizard with progress details and logs
VERBOSE=1 ./startup.sh

1. Before installing SigningHub with an existing database, run the database scripts provided on the Prerequisites page.

---

Wizard Flow

The installation wizard takes you through these steps:

---

Step 1: Select Installation Type

The wizard presents three options:

  1) FIRST TIME          - New SigningHub deployment with database setup
  2) EXISTING DATABASE   - Connect to existing database
  3) REGULAR RELEASE     - Update existing running containers with the new release

Select an option (e.g., 2 for EXISTING DATABASE) and confirm output:

[✓ SUCCESS] Selected: FIRST TIME - New SigningHub deployment

---

Step 2: Configure Mandatory Settings

You will be prompted to enter:

1. Public Host Configuration

   • IP address or hostname where SigningHub will be accessible.

   • Examples: 192.168.1.100, mydomain.com

   • Wizard output confirms:

     [✓ SUCCESS] Public Host set to: 192.168.3.241

2. SigningHub Package Configuration

   • Select an option (e.g., 1 2) to confirm the SigningHub Package, in case multiple .zip files are available in the directory. In case of a single .zip file, no confirmation will be required.

   • Wizard output confirms:

     [✓ SUCCESS] Found SigningHub package: SigningHub-v10.0.3-RR-Lin64-12Sep2025.zip

---

Step 3: Select Database Type

Choose the database to use:

1) MSSQL
2) ORACLE 

Confirm output:

[✓ SUCCESS] Selected: MSSQL - Microsoft SQL Server

---

Step 4: Select Installation Mode

Against the installation mode, only the custom mode is supported, with the existing database.

[✓ SUCCESS] Installation Mode: Custom Mode (required for EXISTING_DATABASE)
[ℹ INFO] Only database credentials will be collected for EXISTING_DATABASE installation

---

Step 5: Configure Custom Settings

Provide the credentials to the existing database:

Database Host: 192.168.2.66
Database Name: sh_db_existing
Database Username: sa
Database Password: [Password]

Confirm output:

[✓ SUCCESS] MSSQL database configurations saved.

---

Step 6: Select Modules to Deploy

Choose which SigningHub services you want to deploy:

  1) Web        - Web application (includes API dependency)
  2) Admin      - Admin panel (includes Admin-API dependency)
  3) Admin-api  - Admin API service only
  4) Api        - API service only
  5) Core       - Core service only
  6) All        - All applications

Confirm output:

[✓ SUCCESS] Selected: all modules

---

Step 7: Configuration Summary

Review the final summary:

Mandatory Settings
  Public Host: 192.168.3.241
  ADSS Server IP: Not required for EXISTING_DATABASE installation
  SigningHub Package: SigningHub-v10.0.3-RR-Lin64-22Sep2025.zip

Installation Type
  Selected: EXISTING_DATABASE 

Database Type
  Selected: MSSQL
  
Selected Modules
  Modules to deploy: web, admin, admin-api, api, core

Database Configurations
  Database Host: 192.168.2.66
  Database Name: sh_db_existing
  Database Port: 1433
  Database Username: sa
  Database Password: [CONFIGURED]
  
Other Settings
  Using existing configuration defaults

---

Step 8: Apply Configuration

Wizard updates all configuration files and confirms:

[✓ SUCCESS] Configuration files updated
[✓ SUCCESS] Configuration completed

---

Step 9: Start Installation

The installation now takes place with info and success messages appearing periodically.

Wizard output:

[ℹ INFO] Starting EXISTING_DATABASE installation...
[ℹ INFO] Selected services: redis mailhog signinghub-admin-api signinghub-web signinghub-admin signinghub-api signinghub-core
[✓ SUCCESS] Infrastructure services are healthy!
[ℹ INFO] Starting admin-api...
[ℹ INFO] Waiting for admin-api to be healthy...
[✓ SUCCESS] admin-api is healthy!
[ℹ INFO] Starting remaining services: signinghub-web signinghub-admin signinghub-api signinghub-core
[✓ SUCCESS] All selected services started successfully!
[✓ SUCCESS] SigningHub services started successfully with the external database!

---

Access Information

When installation is complete, the wizard displays the access URLs:

🌐 SigningHub Web:            https://192.168.1.100:8080
🔧 SigningHub Admin:          https://192.168.1.100:8081
🔐 SigningHub Admin API:      https://192.168.1.100:8084
📡 SigningHub API:            https://192.168.1.100:8082
⚙️ SigningHub Core:           https://192.168.1.100:8086

---

1. The Docker images for SigningHub were built using Debian GNU/Linux as the base operating system.

2. To stop and remove all containers, networks, and volumes, run the following command. This will completely remove the deployed containers and associated data volumes. docker compose --profile existing-database down -v If you want to run the installer a second time, you should first stop and remove any already running containers. After that, run the ./state-remove.sh script to remove the state, and then you can initialise the startup again.

3. If you want to view other Docker-related commands, refer to the README.md file in the SigningHub Docker Package.