> For the complete documentation index, see [llms.txt](https://docs.signius.eu/manuals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.signius.eu/manuals/signius-sealing-server-and-client/signius-sealing-server-dashboard/configuration.md).

# Configuration

## SIGNIUS Sealing Server Dashboard

### Windows and Linux

* Move to "\<http server webapps location>/<**SIGNIUS Sealing Server Dashboard** webapp>/assets/".&#x20;
* open config.json, adjust **SIGNIUS Sealing Server** url if needed and save.
* restart Your http server.

### Docker

#### initial configuration

* Create and adjust docker-compose.yml
  * nano docker-compose.yml

content example:

{% code title="docker-compose.yml" overflow="wrap" lineNumbers="true" %}

```yaml
version: '3.8'

services:
  sseal_dashboard:
    image: sseal-server-dashboard-image:v0.0.0
    container_name: signius-sealing-server-dashboard-container
    volumes:
      - ./config.json:/usr/share/nginx/html/assets/config.json
      - ./nginx.conf:/etc/nginx/conf.d/default.conf
    ports:
      - 80:80
```

{% endcode %}

* build and run container with compose in detached mode (from the directory where docker-compose.yml is located)
  * docker compose up -d

#### later updates

* Move to mapped volume on host.&#x20;
  * open config.json, adjust **SIGNIUS Sealing Server** url if needed and save.
  * open nginx.config, adjust to Your preferences and save.
  * replace the SSL elements/content
* Go to directory with docker-compose.yml
* Rebuild container
  * schema:
    * docker stop \<container\_name or container\_id>
    * docker compose up -d
  * example:
    * docker stop signius-sealing-server-dashboard-container
    * docker compose up -d

{% hint style="info" %}
There are many ways to achieve desired configuration, so this is just a suggestion for a simple yet flexible setup.
{% endhint %}

## SIGNIUS Sealing Server

{% hint style="info" %}
Before proceeding with configuration of server components we suggest:

1. Creating new root level (admin) user with more complex password than the default one.&#x20;
2. Once that done relog to the created (admin) user.
3. Remove the default root (admin) user.&#x20;
4. Save credentials to new root level (admin) user in secure location.
   {% endhint %}

#### Server configuration should proceed in the following order:

* Tenants (at least 1 is needed)
* HSMs (at least 1 is needed)
* TsaSettings (at least 1 is needed)
* Processes
* Users
* Crons

#### Default admin credentials (for first login to the SIGNIUS Sealing Server Dashboard)

* email address:
  * root
* password:
  * root