aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md15
1 files changed, 1 insertions, 14 deletions
diff --git a/README.md b/README.md
index ea1f3f7..f8a2e1c 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
<!--
-SPDX-FileCopyrightText: 2022 Patrick Spek <p.spek@tyil.nl>
+SPDX-FileCopyrightText: 2023 Patrick Spek <p.spek@tyil.nl>
SPDX-License-Identifier: AGPL-3.0-or-later
-->
@@ -65,19 +65,6 @@ called for the `add`, `sync`, end `del` subactions respectively. Using these
functions, one can automate the setup, synchronization, or disabling of certain
components of a system.
-#### Local
-
-A local playbook is simply a directory made in `/etc/bashtard/playbooks.d` with
-the two files specified earlier.
-
-#### Remote
-
-A remote playbook is recorded in `/etc/bashtard/playbooks.d/remotes`. This is a
-space-seperated file, containing 3 columns per line, `name`, `url`, and
-`branch`. When the `sync` subcommand is called, the latest commits on the
-specified `branch` are pulled before calling `playbook_sync()` on them. The
-structure of the actual playbook is the same as a local one.
-
### SSH
Bashtard comes with an `ssh` subcommand to allow the user to run any command on