Admiral, the Shippable Server installer

Shippable Server is a DevOps platform that help teams ship software more frequently and predictably by unifying DevOps tools and activities into assembly lines with rich logistics. It can run behind your corporate firewall thereby allowing you to securely connect to your repositories running on your intranet and run CI/CD flows on them. Shippable Server natively integrates with GitHub Enterprise, Bitbucket Server, and Gitlab Enterprise. User management, permissions, and source code repositories are synced with your source control provider.

Admiral CLI is used to install Shippable Server. A server license is required to install Shippable. For more information, contact us.

Admiral CLI installs the basic dependencies and a user interface to complete the installation and manage the configuration of options. Both of these are available in the Admiral GitHub repository.

The Admiral CLI

The CLI supports the following commands.

$ ./ --help
    ./ <command> [flags]

    ./ install --help

    install         Run Shippable installation
    upgrade         Run silent upgrade without any prompts
    restart         Restart all services
    help            Print this message
    clean           Remove shippable containers and configurations
    info            Print information about current installation
    list            Print available admiral versions
    switch          Switch admiral to a given version


This command will install dependencies, pull any updated images, install the database, and start the Admiral UI. From the cloned Admiral repository, run ./ install.

Install will first generate SSH keys for internal use (if they don't already exist), determine which version was selected from the checked-out tag, generate a login token for use with the UI, and prompt for any information it needs to set up. These are the things it will prompt for:

  • Installer Access Key: This is the key you were provided by Shippable with your server license. If you don't have one, contact us. You can also specify this key using the --installer-access-key argument.
  • Installer Secret Key: The secret key you received with the installer access key. You can also specify this key using the --installer-access-key argument.
  • If you want to install all the stateful services(rabbitmq, redis, gitlab, vault) also on this machine. You can also specify onebox installation using the --onebox argument.
  • Current IP Address: This should be an accessible address for the current machine. It will be the address at which you will access the installer UI and is used for any other services you decide to install on this machine. In most cases, this will be the external IP address.
  • Database IP Address: Enter "D" to run the database on this instance as a container. If you would like it installed somewhere else, enter that address. If you select another location, you will also be asked if it is a new or existing database. Enter "I" to install a new database at that location.
  • Database password: This will be the password for the database user apiuser. Enter a secure password to be set in the database installation.

Confirm that the required values have been entered correctly. If you have decided to install your database in a different location, copy the command displayed and run it on that machine as well to grant SSH access for the installer.

Admiral will then install dependencies, pull Docker images, and install the database. This may take several minutes. When it is complete, the location of the Admiral UI and the login token are printed. Navigate to the UI location in a web browser and enter the given access key to access the installer UI. The rest of the services will be started from there.


This command will upgrade the Shippable installation. For more detailed instructions, please go here.


This is a helper command to recover from unexpected machine shutdown or reboot. If one (or more) Shippable services go down for any reason, this command can be used to restart those services. ./ restart will go through all the components of the system and (re)start them. This command is idempotent, so running it multiple times has no side effects on the system.


The info command displays some basic information about the current installation. Running ./ info from the cloned Admiral repository will print the current version installed, the addresses of the Admiral UI and database, and the login token for Admiral. The version shown may not be the version running if Admiral has been updated but the services have not yet been upgraded.


The list command will list all the available versions for admiral. Running ./ list command will fetch latest tags from git and list them. You can switch admiral to any given version using ./ switch <version_name>. This command is available for v5.7.4 and above.


The switch command checks out the admiral version listed in ./ list command. You can update your admiral server using ./admiral switch <version_name> then run ./ upgrade to run against the version that has been checked out. Please note that this feature is available for admiral v5.7.4 and above, so switching to an earlier version would mean manually checking out latest version using git checkout tags/<version>

The Admiral UI

After running ./ install, the Admiral UI will be available. All further configuration of a new installation takes place here.

There are three distinct sections in the Admiral UI: initializing infrastructure, installing core components, and enabling add-ons.

Initializing infrastructure

The first panel is to initialize infrastructure. Select where each of the listed components will run, enter the passwords, and click initialize. Components running on the same node as Admiral will be started in Docker containers, and components elsewhere will be installed outside of a container.

Installing core components

After initializing the infrastructure, select which provider(s) will be available on your installation and which mail service you will use, entering the details requested for both. Then click install. At this point, you will be able to log into your local version of Shippable.

Enabling add-ons

Additional optional services and integrations may be enabled from this panel. For example, you can enable various hub integrations for your users to push or pull from Docker registries.

Enabling caching

To enable caching, navigate to the Build configuration section in the Configure and Install panel. Select the Upload artifacts to AWS option. Click on Save and Restart Services. To learn more about the benefits of caching, go here.


The installer stores files in /etc/shippable. These files include configuration information, keys, and initialization scripts. The following are found in /etc/shippable.


The admiral.env file contains values used by Admiral for your installation. Any values requested by the CLI are stored here, as are other values which only Admiral needs to access. Editing your admiral.env file directly is not recommended.

The following values are stored in admiral.env:

  • LOGIN_TOKEN: The token used to log into the Admiral user interface. This is also shown at the end of ./ install and displayed by ./ info.
  • DB_IP: The location of the database set when first running ./ install. This is also displayed by ./ info.
  • ADMIRAL_IP: The location of Admiral set when first running ./ install. This is also displayed by ./ info.
  • ACCESS_KEY: The installer access key entered when first running ./ install. This is used to pull Docker images.
  • SECRET_KEY: The installer secret key entered when first running ./ install. This is used to pull Docker images.
  • SERVICE_USER_TOKEN: The Shippable API token created for the internal service user. This will be set by Admiral when initializing the database.
  • RELEASE: The current Admiral release version. Set by ./ install, this will be set to the repository tag.
  • IS_SERVER: This should be true.
  • DB_PORT: The database port, set by ./ install.
  • DB_USER: The user that Admiral and Shippable API will use to connect to the database. This will be apiuser.
  • DB_NAME: The name of the database used by Admiral and Shippable API. This will be shipdb.
  • DB_PASSWORD: The Postgres password for apiuser.
  • DB_DIALECT: This will be postgres.
  • DB_INSTALLED: A Boolean denoting if the database has been installed. It will be set to true when connecting to an existing database or once the database is installed.
  • RUN_MODE: This may be dev or production and determines the log level of Shippable services.
  • SSH_USER: This will be root.
  • PUBLIC_IMAGE_REGISTRY: The registry containing the public images used by the installer.
  • PRIVATE_IMAGE_REGISTRY: The registry containing the private images used by the installer.
  • VAULT_URL: The location of Vault. This will be set by Admiral when initializing infrastructure.
  • VAULT_TOKEN: The root token for Vault. This is also set by Admiral when Vault is initialized.
  • VAULT_UNSEAL_KEY1: The first of five unseal keys for Vault, this is set when Admiral installs Vault. This will not be set when connecting to an existing Vault installation.
  • VAULT_UNSEAL_KEY2: The second of the five unseal keys.
  • VAULT_UNSEAL_KEY3: The third of the five unseal keys.
  • VAULT_UNSEAL_KEY4: The fourth of the five unseal keys.
  • VAULT_UNSEAL_KEY5: The fifth of the five unseal keys.
  • SWARM_WORKER_JOIN_TOKEN: The worker join token for Docker Swarm. This will be set by Admiral when initializing the swarm master.

machinekey and

Admiral creates a SSH key pair to use to connect to other hosts. The keys are stored in machinekey and and will be used when installing components on other nodes. It will also be used as the SSH key when initializing system nodes.


This folder contains SQL scripts run by Admiral in database initialization and when upgrading to a new version.


This folder contains files relating to the message queue infrastructure component with rabbitmq.conf and a scripts folder.


This folder contains files for the Redis initialization including redis.conf and a scripts folder.


This folder contains files for Vault initialization including config.hcl and local.json and a scripts folder with policy.hcl and vault.conf.


This folder contains files for initializing the state storage infrastructure component such as gitlab.rb, gitlab-secrets.json, ssh_host_ecdsa_key,, ssh_host_ed25519_key,, ssh_host_rsa_key, and scripts and Trusted-certs folders.


This folder contains files for initializing the secret storage infrastructure component.


This folder contains files for initializing the Swarm workers.


The installer also stores files in /var/lib/shippable. These files contain data for the components and services started by the installer. The following subdirectories are in /var/lib/shippable.


The db folder contains a data folder that is used to store the database information when installing the database on the same node. This folder allows the container to be restarted if necessary.


The logs folder contains logs saved by the installer. The logs are organized by component.


The msg folder contains a data folder. This is used as a mounted volume when running RabbitMQ in a container.


The redis folder contains a data folder. This is used as a mounted volume when running Redis in a container.


The secrets folder contains a data folder. This is used as a mounted volume when running Vault in a container.


The state folder contains data and logs subdirectories. These are both used as mounted volumes when running GitLab in a container.


The master folder may contain a data folder. It's not used at this time.


The workers folder contains a data folder. It's not used at this time.