Oops, update the README to match the newly-renamed setup-machine.yml
This commit is contained in:
parent
a9db85d7c8
commit
24ea2b9de1
1 changed files with 3 additions and 3 deletions
|
@ -9,8 +9,8 @@ We like to use Ansible playbooks to keep track of how we set up our servers,
|
|||
here's how we've structured them! (We don't use very fancy Ansible features, we
|
||||
just use them as idempotent command-line scripts!)
|
||||
|
||||
- `setup-users.yml`: Sets up the user accounts for the system, with their SSH
|
||||
keys for login.
|
||||
- `setup-machine.yml`: Sets up the hostname config and user accounts for the
|
||||
system, with their SSH keys for login.
|
||||
- `setup-security.yml`: Sets up firewall rules and automatic system updates.
|
||||
(This is a standard playbook I use for all my servers!)
|
||||
- `setup-forgejo.yml`: Sets up the Forgejo server itself, as a `systemd`
|
||||
|
@ -25,7 +25,7 @@ If you're interested in setting up your own Forgejo service, this could be
|
|||
useful as a starting point, there's not much custom here! Just a couple things
|
||||
to note:
|
||||
|
||||
- `setup-users.yml` contains my own username and my own SSH public keys—you'll
|
||||
- `setup-machine.yml` contains my own username and my own SSH public keys—you'll
|
||||
want to replace those! (Public SSH keys aren't secret, don't worry, I'm fine!)
|
||||
- `files/app.ini` includes some custom config you'll need to replace, like our
|
||||
domain name. (We also opt to use Forgejo's built-in HTTPS support, via
|
||||
|
|
Loading…
Reference in a new issue