From 24ea2b9de124aaf6ef884d44ecbe338a47bdf091 Mon Sep 17 00:00:00 2001 From: Emi Matchu Date: Mon, 10 Jun 2024 13:04:56 -0700 Subject: [PATCH] Oops, update the README to match the newly-renamed setup-machine.yml --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b390374..142fbae 100644 --- a/README.md +++ b/README.md @@ -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