Skip to main content

Application Settings

Application settings live on the application detail page under Settings and in the right-side control panels.

Source Summary​

The source section shows:

  • Repository.
  • Branch.
  • Build method.
  • Port.

Use this section to confirm the app is deploying from the expected source before triggering a new deployment.

Domains​

The domains section shows:

  • Generated Moltern URL.
  • Custom domain input.
  • Verification status.
  • Records to copy to your domain provider.
  • Check now action for pending domains.
  • Remove action.

Add custom domains only after the generated Moltern URL works.

Runtime​

Runtime settings include:

  • Port.
  • Health check path.

The port must match the port your app listens on. The health check path should return quickly and successfully when the app is healthy.

File Storage​

Web service apps can enable shared filespace.

Settings include:

  • Enabled or disabled.
  • Mount path, such as /data.
  • Access mode: read/write or read-only.

Use shared filespace for files the app must retain across deploys. Do not use the application container filesystem for important persistent data unless shared filespace is enabled.

Environment Variables​

The variables section supports:

  • Individual edit mode.
  • Bulk edit mode.
  • Build-time flag per variable.
  • Write-only handling for sensitive names.
  • Deleting variables.

See Environment Variables And Secrets.

Build Overrides​

Build override fields include:

  • Install command.
  • Build command.
  • Start command.

Use overrides when auto-detection needs help.

Examples:

pnpm install --no-frozen-lockfile
pnpm run build
node build/index.js

Keep commands short and reproducible.

Size Controls​

For supported web service apps, size controls include:

  • Replicas.
  • CPU per replica.
  • RAM per replica.
  • Preview button.
  • Apply button.
  • Billing impact and plan warnings.

Always preview before applying.

Delete App​

Deleting an app removes the app workload from Moltern.

Before deleting:

  • Confirm it is the correct environment.
  • Confirm no active domain should remain attached.
  • Confirm logs or release history are no longer needed.
  • Confirm the owner approved removal.

Deletion cannot be used as a rollback strategy. Use a new deployment or static-site promotion when you need to restore a version.