Skip to content

Commit 93d16b8

Browse files
committed
Update Readme
1 parent 692f47e commit 93d16b8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ One possible solution is to:
1515
* Run `./manage.py makemigrations`, so that it creates new initial migrations
1616
* Run `./manage.py migrate --fake [new migrations]` or `./manage.py migrate --fake-initail` on all servers.
1717

18-
This workflow might work fine, if you have only few (production) servers - however, it becomes hard, when you have many environments with different versions of your application.\
18+
This workflow might work fine, if you have only few (production) servers - however, it becomes hard, when you have many environments with different versions of your application.
1919

2020
With django-replace-migrations also creates new initial migrations, but also, additionally, adds the already existing migrations to the `replace` list of the new migration
2121
(That list is used by `squashmigrations` as well). By doing that, faking migrations is not needed anymore.
@@ -44,7 +44,7 @@ If your apps are not depending on each other, you can use django-replace-migrati
4444
```
4545
./manage.py makemigratons --replace-all --name replace [app1, app2, ...]
4646
```
47-
Note, that you will need to list all of your apps explicitly - otherwise django will also try to replace migrations from dependencies.
47+
Note, that you will need to [list all of your apps](https://stackoverflow.com/questions/4111244/get-a-list-of-all-installed-applications-in-django-and-their-attributes) explicitly - otherwise django will also try to replace migrations from dependencies.
4848
While `--name` could be omitted, it is highly recommended to use it so that you can easily recognize the new migrations.
4949

5050
If for any of your apps there are not one but two or more migrations created, your apps are depending on each other (see below).
@@ -70,9 +70,9 @@ The workflow for this would be:
7070
* commit and note the commit hash
7171
* `git checkout 2.0`
7272
* create a new branch `git checkout -b 2-0-replace-migrations`
73-
* run `./manage.py makemigrations --replace-all --name replace_2_0 [app1, app2, ...]`
73+
* run `./manage.py makemigrations --replace-all --name replace_2_0 [app1, app2, ...]` ([How to get all apps](https://stackoverflow.com/questions/4111244/get-a-list-of-all-installed-applications-in-django-and-their-attributes))
7474
* commit and note the commit hash
75-
* `git checkout [your main branch]`
75+
* `git checkout [your main/feature branch]`
7676
* `git cherry-pick [commit-hash from 2-0-delete-migrations]`
7777
* `git cherry-pick [commit-hash from 2-0-replace-migrations]`
7878

0 commit comments

Comments
 (0)