Documentation
Deploy applications

Service Settings

Learn how to configure your services.

Open your service from its project to view settings.

Settings

See Deploying a Service for individual settings. Updating configuration triggers a redeploy.

Settings that can't be changed are:

  • the deploy source, you can't switch from GitHub to a registry (or vice versa)
  • whether the service is exposed publically or it is accessible on your server only
  • the protocol to communicate with your service (HTTP, TCP, UDP)
  • the server this service has been deployed to

To change these settings, use Deploy Copy from the service’s three-dot menu on the project page.

Deploy rules

Use deploy rules to control which repository changes trigger deployments, particularly in monorepos.

  • Autodeploy: Toggle this, if you want to deploy new commits automatically. Otherwise, you can use the deploy hook to trigger new deploys.
  • Include Paths: Only deploy if the commit contains changes in one of the included paths.
  • Ignore Paths: Exclude matching files from triggering a deployment.

Paths accept filenames or glob patterns.

A deployment runs when at least one changed file is not ignored and matches the include paths (or no include paths are set).

For example, with src/** included and **/*.md ignored, changing src/app.ts and README.md together triggers a deployment. Changing only README.md does not.

Glob Patterns

Glob patterns match filenames using wildcards: * matches any sequence of characters (except /), ? matches any single character, and character classes like [abc] match any enclosed character. Common examples: src/backend/**/*, src/frontend/**/*, src/**/*, package.json.

Restart or redeploy

Choose Restart to stop and start the existing container without rebuilding it. This briefly interrupts the service.

Choose Redeploy to run the deployment process again. After changing environment variables, use Save and redeploy to apply them.

Service Info

Service Status

Service status:

  • Up if everything is fine,
  • Down if your service has been deployed, but it is currently not running.
  • Paused if your service is paused.
  • Restarting while a restart is in progress.
  • Pending if your service has not yet been deployed, but the deploy is in progress.

Deploy Status

The deploy status shows

  • Deploy Live for successful deploys,
  • Deploy Failed for unsuccessful deploys,
  • Deploy in Progress for deploys in progress.

Deploy status is separate from service status. See what happens when a deployment fails.

Deploy Hook

A GET request to this URL triggers a new deployment. Keep the URL secret: anyone with it can trigger deployments.

You can rotate the hook from the service page. This immediately invalidates the old URL; update it in any integrations that use it.

Domain / Internal Host

Public services show their sliplane.app address; TCP and UDP addresses include a port. Private services show an internal hostname for connections from the same server.

Repository

If you deployed from GitHub, you can find a link to your GitHub repository here.

Public Image

If you deployed from a container registry, you can find a link to the image here.

Server

This links to the server, where your service was deployed on.

How is this guide?

On this page