Applications
Link a server to an application
Choose which servers receive deploys for an application.
On first deploy, Devopness usually links a server automatically. Use this page when you need to add servers, change targets, or set the destination explicitly.
Goal
Update the server list for an application.
What you need
- Permission to update the application
- The application selected in the correct environment
- The server or servers that should receive deploys
Using Devopness MCP
Try these prompts in Devopness MCP:
- "Link the
web-1server toacme-web" - "Attach the production servers to
acme-api" - "Link the staging server to the
acme-apiapplication"
After you save
- The linked server appears in the application server list
- Future deploys can target the linked servers
Verify
- The server appears in the linked servers list
- A deploy uses the servers you expect
Common issues
- The server does not appear in the list: confirm it belongs to the selected environment
- You cannot link the server: confirm you have update permission for the application
- The link disappears after refresh: confirm the save completed
What to do next
- Deploy the application
- Add a virtual host when the app needs a public URL
- Add a daemon or cron job for private or scheduled workloads
Required permissions
To follow this guide, you need the following permissions in the target environment.
| Resource Type | Required Permission |
|---|---|
| Application | Edit |
For instructions on how to grant user permissions to an environment, please follow the guide Add a team to an environment.