search

Installation via domain

This page provides a step-by-step walkthrough of the installation wizard for SigningHub installation using a domain name instead of an IP address. In the walkthrough below, a fresh installation is being performed using the default MSSQL database configuration.

circle-info

hashtag
NGINX Deployment Flexibility in Docker Installer

The Docker deployment now provides enhanced flexibility by allowing users to choose between using a bundled NGINX instance or integrating with an externally managed NGINX setup.

External NGINX Integration (IP-based Deployment)

  • If the client chooses to use their own NGINX instance, the deployment must be performed using an IP address.

  • In this mode:

    • The Docker installer will not deploy or configure an NGINX container.

    • The client is responsible for configuring their external NGINX.

    • The external NGINX must be connected to the same Docker network as the application containers to ensure proper communication.

Bundled NGINX (Domain-based Deployment)

  • If the client opts to use the NGINX provided by the Docker package, the deployment must be performed using a domain name.

  • In this mode:

    • The Docker installer will automatically create a dedicated NGINX container.

    • All required NGINX configurations will be automatically generated and applied.

Important Notes

  • IP-based deployment → External NGINX only (no NGINX container installed).

  • Domain-based deployment → Bundled NGINX is automatically installed and configured.

  • External NGINX must reside on the same Docker network as the application containers; otherwise, connectivity issues may occur.

hashtag
Run Interactive Installation

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

hashtag
Wizard Flow

The installation wizard takes you through these steps:

hashtag
Step 1: Configure Mandatory Settings

You will be prompted to enter:

  1. Public Host Configuration

    • Enter the hostname where SigningHub will be accessible.

    • Examples: mydomain.com

    • Wizard output confirms:

  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:

hashtag
Step 2: Select Installation Type

The wizard presents two options:

Select an option (e.g., 1 for FRESH INSTALLATION) and confirm output:

hashtag
Step 3: Configure ADSS Server

Enter the host IP or domain name where the ADSS Service is deployed:

hashtag
Step 4: Select Database Type

Choose the database to use:

Confirm output:

hashtag
Step 5: Select Installation Mode

Depending on your selected database type:

  • For MSSQL:

    Confirm output:

circle-info

  1. Oracle database requires custom configuration - Default mode not available

hashtag
Step 6: Select Modules to Deploy

Choose which SigningHub services you want to deploy:

Confirm output:

hashtag
Step 7: Configure Custom Subdomains (Domain Deployment)

Either provide a custom subdomain for the selected modules, or press 'Enter' to use default subdomains.

hashtag
Step 8: Configuration Summary

Review the final summary:

hashtag
Step 9: Apply Configuration

Wizard updates all configuration files and confirms:

hashtag
Step 10: Start Installation

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

Wizard output:

hashtag
Access Information

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

hashtag
Post Installation

If you are using a custom domain name, after installation, you must replace your custom domain certificate and key in the following path:

The certificate and key file names must match the domain name you provided in Step 1 (Publish Host and Package Configuration). For example:

  • If the domain name is signinghub.com, the files should be named as:

    • signinghub.com.crt

    • signinghub.com.key

  • Ensure the machine IP is mapped in the DNS so that the domain is accessible.

circle-info

  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 first-time down -v To remove the nginx container, run the following command: docker compose --profile domain 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.

PreviousRegular release installationNextSigningHub OEM Distribution & Branding

Last updated

Was this helpful?