about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorBen Morrison <ben@gbmor.dev>2020-05-28 18:32:07 -0400
committerBen Morrison <ben@gbmor.dev>2020-05-28 18:32:07 -0400
commit8d0f0b4e0d934d8af6c340d9e975e53bc43ab2c4 (patch)
tree9b67f5979ccd16bc8df97795dfec54777791f8e0
parent2cb85a4f5922be57a43470bde828d8f92138de40 (diff)
downloadclinte-8d0f0b4e0d934d8af6c340d9e975e53bc43ab2c4.tar.gz
clarified upgrade process and note section v2.0.0
-rw-r--r--README.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/README.md b/README.md
index 6814110..10485d5 100644
--- a/README.md
+++ b/README.md
@@ -42,11 +42,11 @@ $ sudo make install
 
 **Note:** v1.0.0 used sqlite3, which presented some issues. v2.0.0 uses a json structure for posts,
 as this will be safer on a multi-user system. When upgrading from v1.0.0 to v2.0.0, you won't be
-able to save your posts without using a third-party tool to dump the `posts` table to json, and
+able to save the posts without using a third-party tool to dump the `posts` table to json, and
 manually adjusting it to fit the expected format (which can be seen in the included `clinte.json`).
 
-*If upgrading from v1.0.0 -> v2.0.0, do a fresh install. The following applies to upgrading when
-already running at least v2.0.0*
+*If upgrading from v1.0.0 -> v2.0.0, do a fresh install, including removing the database directory 
+`/usr/local/clinte`. The following applies to upgrading when already running at least v2.0.0*
 
 ```
 $ make update
@@ -111,4 +111,5 @@ Use this flag if something's going wrong. Additional information will be written
 
 ## Notes
 
-The file where the posts are stored must be writeable by all users on the system. Keep this in mind.
\ No newline at end of file
+The file where the posts are stored, `/usr/local/clinte/clinte.json`, must be writeable by all
+users on the system. Keep this in mind.
\ No newline at end of file