Skip to content

Commit cd5b237

Browse files
author
Ben Moody
committed
Update readme for the short term
1 parent 5266a33 commit cd5b237

File tree

2 files changed

+6
-47
lines changed

2 files changed

+6
-47
lines changed

README.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,12 @@ published here in case they are useful for other scuttlebutt/nostr users.
1111
2. Run `ansible-galaxy install -r requirements.yml`
1212

1313
# Running ansible against Droplets created under the `terraform` repository
14-
All new droplets created using the [terraform repo](https://github.com/verse-pbc/terraform) will require the use of the [ansible_ssh_key](./ansible_ssh_key).
15-
This key is encrypted with ansible-vault, and can be decrypted with a call to `ansible-vault decrypt ./ansible_ssh_key`, so you can use it locally while executing
16-
playbooks. Just remember to always re-encrypt it before pushing to Github.
14+
All new droplets created using the [terraform repo](https://github.com/verse-pbc/terraform) will begin with only `DEFAULT_DROPLET_ROOT_SSH_KEY`, which is
15+
securely stored in DigitalOcean. Individual admin users are created on a Droplet, and have their SSH keys added, through
16+
the [ssh-config-and-harden](./roles/ssh-config-and-harden) role. In the next few week, this playbook will be automatically
17+
executed against new Droplets upon creation, so user SSH access for running Ansible scripts against new Droplets will
18+
be available for those configured during Droplet-creation. In the short-term, though, you can message Ben, and he can
19+
execute the `ssh-config-and-harden` role against the new Droplet to grant access.
1720

1821
# Repo structure
1922

ansible_ssh_key

Lines changed: 0 additions & 44 deletions
This file was deleted.

0 commit comments

Comments
 (0)