diff options
| author | Ben Morrison <ben@gbmor.dev> | 2020-06-16 15:08:11 -0400 |
|---|---|---|
| committer | Ben Morrison <ben@gbmor.dev> | 2020-06-16 15:08:11 -0400 |
| commit | 69ad4de4caacb0464a17a57b42219268dad10691 (patch) | |
| tree | 73d7cb2083a2541ac26ed672cd7b9ec66bd06b7e | |
| parent | ad215ba851fa0c67ff657d76b1865ab2501af715 (diff) | |
| download | clinte-69ad4de4caacb0464a17a57b42219268dad10691.tar.gz | |
changed upgrade steps
changed refs to v2.0.0 -> v2.x
| -rw-r--r-- | README.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/README.md b/README.md index 73f7486..2797ac8 100644 --- a/README.md +++ b/README.md @@ -40,18 +40,18 @@ $ sudo make install ## Upgrading -**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 +**Note:** v1.0.0 used sqlite3, which presented some issues. v2.x uses a json structure for posts, +as this will be safer on a multi-user system. When upgrading from v1.0.0 to v2.x, you won't be 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, including removing the database directory +*If upgrading from v1.0.0 -> v2.x, 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 $ make -$ make upgrade +$ make install ``` This will: |