Service Dependencies

Table of Contents

1. Introduction
2. GUI
3. CLI Option: --deps
4. CLI Example

Introduction

Servy supports optional service dependencies, allowing a service to start only after one or more other Windows services are running.
Enter each dependent service by its service name (not the display name) on a new line or separate them with semicolons (;).

This ensures that your service starts in the correct order and avoids errors if required services are not yet running.

GUI

The advanced tab provides additional configuration options such as service dependencies.

CLI Option: --deps

The --deps command-line option lets you specify one or more Windows service dependencies when installing a service via the CLI.

• Syntax: --deps="Service1; Service2; Service3"
• Servy will wait for all specified services to be running before starting the main service.
• Multiple dependencies can be separated with semicolons or listed on separate lines in the configuration file.
• This is especially useful for applications that rely on databases, message brokers, or other background services.

CLI Example

servy-cli install `
  --name="My NodeJS Service" `
  --description="My NodeJS Server" `
  --path="C:\Program Files\nodejs\node.exe" `
  --startupDir="C:\Apps\App" `
  --params="C:\Apps\App\index.js" `
  --startupType="Automatic" `
  --deps="MongoDB; MySQL80" `

Tip: You can combine service dependencies with pre-launch scripts and health checks to ensure that your service starts reliably in complex environments.