Users and SSH Keys

Create, manage, and upload SSH keys to Drycc for use in deploying and connecting to applications.

For Dockerfile and Buildpack based application deploys via git push, Drycc Workflow identifies users via SSH keys. SSH keys are pushed to the platform and must be unique to each user. Users may have multiple SSH keys as needed.

Generate an SSH Key

If you do not already have an SSH key or would like to create a new key for Drycc Workflow, generate a new key using ssh-keygen:

$ ssh-keygen -f ~/.ssh/id_drycc -t rsa
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/admin/.ssh/id_drycc.
Your public key has been saved in /Users/admin/.ssh/
The key fingerprint is:
3d:ac:1f:f4:83:f7:64:51:c1:7e:7f:80:b6:70:36:c9 [email protected]
The key's randomart image is:
+--[ RSA 2048]----+
|              .. |
|               ..|
|           . o. .|
|         o. E .o.|
|        S == o..o|
|         o +.  .o|
|        . o + o .|
|         . o =   |
|          .   .  |
$ ssh-add ~/.ssh/id_drycc
Identity added: /Users/admin/.ssh/id_drycc (/Users/admin/.ssh/id_drycc)

Adding and Removing SSH Keys

By publishing the public half of your SSH key to Drycc Workflow the component responsible for receiving git push will be able to authenticate the user and ensure that they have access to the destination application.

$ drycc keys:add ~/.ssh/
Uploading to drycc... done

You can always view the keys associated with your user as well:

$ drycc keys:list
ID                              OWNER    KEY                           
[email protected]        admin    ssh-rsa abc AAAAB3Nz...3437.local
[email protected]           admin    ssh-rsa 123 AAAAB3Nz...nius.local

Remove keys by their name:

$ drycc keys:remove [email protected]
Removing [email protected] SSH Key... don