You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,15 +28,15 @@ You'll very likely want to put RecipeSage behind a reverse proxy for SSL termina
28
28
29
29
### Updating
30
30
31
-
First, _take a look at the changelog below for any special upgrade notes_. Then follow the steps below.
32
-
33
31
By default, the database will be automatically migrated when updating to a new container version. As with any migration/upgrade, I **strongly recommend taking a backup** of your volumes before migrating to avoid any potential data loss. My first recommendation when encountering issues after an update will be to rollback, which will be impossible if you don't have a backup.
34
32
35
-
Update your local copy of this repo with the latest from this repository. If cloned with Git, this is as simple as `git pull`.
33
+
1.[_Take a look at the changelog below for any special upgrade notes_](#changelog). Then follow the steps below.
34
+
35
+
2. Update your local copy of this repo with the latest from this repository. If cloned with Git, this is as simple as `git pull`.
36
36
37
-
Update your local images: `docker compose pull`.
37
+
3.Update your local images: `docker compose pull`.
38
38
39
-
Then, down & up the containers: `docker compose down --remove-orphans && docker compose up -d`
39
+
4. Down & up the containers: `docker compose down --remove-orphans && docker compose up -d`
40
40
41
41
<br />
42
42
@@ -100,11 +100,11 @@ The `ingredient-instruction-classifier` container facilitates machine learning c
100
100
101
101
Migrations are now automated, and use a different migration tool.
102
102
103
-
If you have an older version of this repository, you _must_ upgrade to this version of the repository and do the following before upgrading to newer versions:
103
+
If you have an older version of this repository, you _must_ upgrade to this version of the repository and do the following before upgrading to newer versions so that migrations all line up:
104
104
105
105
1. Update your local copy of the repository to v4.0.0
106
106
2. Run `docker compose exec api tsx packages/backend/src/migrate`
107
-
3.Run`docker compose exec api npx prisma migrate resolve --applied 0_init`
107
+
3.If the command prior ran successfully, run`docker compose exec api npx prisma migrate resolve --applied 0_init`
0 commit comments