mirror of
https://github.com/pinry/pinry.git
synced 2026-01-15 03:32:05 +01:00
doc: add description for tokens reset
This commit is contained in:
@@ -6,13 +6,29 @@ This doc is about how you should do to upgrade specified version to next version
|
|||||||
Generally, you should have no extra action to take if you use our docker version
|
Generally, you should have no extra action to take if you use our docker version
|
||||||
if we haven't written notes for it.
|
if we haven't written notes for it.
|
||||||
|
|
||||||
How to get the current version:
|
If you meet some errors which include `no such table`, please have a try to run migrations in docker:
|
||||||
|
```
|
||||||
|
# out of docker
|
||||||
|
docker exec -it <your-container-id> bash
|
||||||
|
# in docker
|
||||||
|
python manage.py migrate
|
||||||
|
```
|
||||||
|
|
||||||
|
How to get the current version with source code:
|
||||||
```
|
```
|
||||||
git tag
|
git tag
|
||||||
```
|
```
|
||||||
The first line of output is our latest version of code.
|
The first line of output is our latest version of code.
|
||||||
|
|
||||||
|
|
||||||
|
# v2.1.6 -> v2.1.7
|
||||||
|
v2.1.6 has a security issue which may cause unauthorized token-read.
|
||||||
|
If you upgrade your instance from v2.1.6 to v2.1.7, you could go into
|
||||||
|
docker and run following command to reset tokens.
|
||||||
|
```
|
||||||
|
python manage.py users_reset_tokens
|
||||||
|
```
|
||||||
|
|
||||||
# v2.0.2 -> v2.1.0
|
# v2.0.2 -> v2.1.0
|
||||||
Main breaking changes:
|
Main breaking changes:
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user