40 lines
1.8 KiB
Markdown
40 lines
1.8 KiB
Markdown
---
|
|
title: Release 0.9
|
|
---
|
|
|
|
Due to some database changes that had to be rather sooner than later, there is no possibility to directly upgrade. You must extract the data before hand and import it again. It is recommended to spin up a second instance of authentik to do this.
|
|
|
|
To export data from your old instance, run this command:
|
|
|
|
- docker-compose
|
|
|
|
```
|
|
docker-compose exec server ./manage.py dumpdata -o /tmp/authentik_dump.json authentik_core.User authentik_core.Group authentik_crypto.CertificateKeyPair authentik_audit.Event otp_totp.totpdevice otp_static.staticdevice otp_static.statictoken
|
|
docker cp authentik_server_1:/tmp/authentik_dump.json authentik_dump.json
|
|
```
|
|
|
|
- kubernetes
|
|
|
|
```
|
|
kubectl exec -it authentik-web-... -- ./manage.py dumpdata -o /tmp/authentik_dump.json authentik_core.User authentik_core.Group authentik_crypto.CertificateKeyPair authentik_audit.Event otp_totp.totpdevice otp_static.staticdevice otp_static.statictoken
|
|
kubectl cp authentik-web-...:/tmp/authentik_dump.json authentik_dump.json
|
|
```
|
|
|
|
After that, create a new authentik instance in a different namespace (kubernetes) or in a different folder (docker-compose). Once this instance is running, you can use the following commands to restore the data. On docker-compose, you still have to run the `migrate` command, to create all database structures.
|
|
|
|
- docker-compose
|
|
|
|
```
|
|
docker cp authentik_dump.json new_authentik_server_1:/tmp/authentik_dump.json
|
|
docker-compose exec server ./manage.py loaddata /tmp/authentik_dump.json
|
|
```
|
|
|
|
- kubernetes
|
|
|
|
```
|
|
kubectl cp authentik_dump.json authentik-web-...:/tmp/authentik_dump.json
|
|
kubectl exec -it authentik-web-... -- ./manage.py loaddata /tmp/authentik_dump.json
|
|
```
|
|
|
|
Now, you should be able to login to the new authentik instance, and migrate the rest of the data over.
|