Configuration Options

Modifying your service settings post-deployment.

You can edit a service by opening its detail page and selecting the Configuration tab. This tab focuses on runtime settings that affect the next deployment.

Editable fields

  • Runtime environment: Change the runtime used to start the app.
  • Host Name: Update the generated subdomain label.
  • Port: Match the internal port your app listens on.
  • Build command: Command run before the app starts.
  • Start command: Command used to run the app.
  • Encrypted secrets: Add, edit, remove, or import environment variables.

Use this page when your app changes shape after the first deploy: a new start file, a different framework port, a renamed branch, extra secrets, or a new hostname. Configuration changes are saved with the service and used on the next deploy.

Updating hostnames

By default, your app is given a randomly generated subdomain. You can change this to a recognizable hostname directly from the configuration panel.

The final URL uses the host name plus the Mapherix domain, for example example.mhserver.dpdns.org. Pick short lowercase names that are easy to type and clearly connected to the project.

Updating deploy settings

Change the build command when dependency installation or asset generation changes. Change the start command when the app entry file changes. Change the port when the process listens on a new internal port. After saving, redeploy so the running service matches the new settings.

Configuration summary

The summary card shows the values that will be used when you click Save and Deploy, including runtime, branch, port, host, and the number of configured secrets.

Saving Changes
Any changes made to the configuration tab require a redeployment. Clicking Save and Deploy will gracefully spin down your old instance and boot a new one with the updated settings.