SSH connections
Give remote work a named destination.
Connect your server and associate an appropriate workspace with a project or conversation.
Give remote work a named destination.
When project files, builds or publication targets live on your own server.
An unexplained server address makes deployments easy to misdirect. Named SSH connections connect the intended server with the project or conversation that needs it.
Configure and test a connection, then assign it to the relevant work. Explain permitted paths and intended operations in the task.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Add a recognisable connection with host, port and supported identity.
- 02
Check the connection status and explicitly select the connection and server folder for the task.
- 03
Describe what may change on the server and which locations are outside the task.
How it could work for you.
Build locally and use a named staging connection for an explicitly requested publication.
How to assess the result
A connection does not by itself authorise changes everywhere on the server. Scope and engine permissions still matter.
Where to find it.
Settings → Access & Tools → SSH; conversation → Tools → SSH
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Connection settings and the selected association are saved. Project files remain on the server.
What you need to know
Connecting does not authorise changes to every server file. Server account permissions and the engine also determine what is technically possible.