How to set up SSH deployment keys on Semaphore 2.0?

[shiroyasha]

trafficstars

We had several similar questions in the community and support.

So far I am directing them to https://docs.semaphoreci.com/article/66-environment-variables-and-secrets.

Opening the issue because this is a very common use case that is not addressed directly in the docs.

[markoa]

@shiroyasha can you post anything (snippets etc) that team has already shared with the users who asked? It would make publishing easier.

[shiroyasha]

Unfortunately no. So far we only pointed out that they can store files in secrets (https://docs.semaphoreci.com/article/66-environment-variables-and-secrets#storing-files-in-secrets), including SSH keys, and attach them to deployment pipelines.

[shiroyasha]

@darkofabijan volountered on standup to take over this issue.

[ahawkins]

Does #237 address this?

[markoa]

@ahawkins What we've seen is that people who ask for this will really benefit from having a page which is only about the topic of adding an SSH key for deployment. What I'd suggest is creating a new PR which is very similar to the one you wrote for private dependencies. Just strip it of GitHub stuff and make it based on the fact that someone has a plain server on an IP address (like when you launch a DigitalOcean droplet) and then semaphore.yml runs a command over ssh as an example.