summaryrefslogtreecommitdiff
path: root/docs/ops.md
diff options
context:
space:
mode:
authorOwen Jacobson <owen@grimoire.ca>2025-06-11 12:39:28 -0400
committerOwen Jacobson <owen@grimoire.ca>2025-06-11 12:39:28 -0400
commit6e6b068ae2adc8c5ef8acb633dcadfbdc3221b61 (patch)
tree79831028416b0d6934f32961a3fc77d8b004369e /docs/ops.md
parent1f009e06fd6db82a91536eec88ef3232267385bf (diff)
tools/reformat
Diffstat (limited to 'docs/ops.md')
-rw-r--r--docs/ops.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ops.md b/docs/ops.md
index 4274e22..4dfec49 100644
--- a/docs/ops.md
+++ b/docs/ops.md
@@ -6,6 +6,6 @@ The `pilcrow` server will automatically upgrade its database on startup. Before
To avoid destroying backups that may still be needed, `pilcrow` will not start if the backup database already exists. **There is no catch-all advice on how to proceed**, but you can try the following:
-* Start the server with **a copy** of the backup database, and determine if any data has been lost. If not, shut it down, replace your main database by copying the backup, and carry on.
+- Start the server with **a copy** of the backup database, and determine if any data has been lost. If not, shut it down, replace your main database by copying the backup, and carry on.
The `pilcrow` database is an ordinary file. While the server is not running, it can be freely copied or renamed without invalidating the data in it.