mirror of
https://github.com/wassname/talk.git
synced 2026-07-15 11:26:58 +08:00
updated docs for 4.1 release
This commit is contained in:
@@ -45,3 +45,5 @@ items:
|
||||
children:
|
||||
- title: Migrating to v4.0.0
|
||||
url: /migration/4/
|
||||
- title: Migrating to v4.1.0
|
||||
url: /migration/4.1/
|
||||
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: Migrating to v4.1.0
|
||||
permalink: /migration/4.1/
|
||||
---
|
||||
|
||||
## Database Migrations
|
||||
|
||||
We have unified the database verifications that were introduced in 3.x.x into
|
||||
the migration system. This unification unfortunately required a database
|
||||
migration bump.
|
||||
|
||||
### Source
|
||||
|
||||
When running via source, you can run the following to start the migration
|
||||
process:
|
||||
|
||||
```bash
|
||||
./bin/cli migration run
|
||||
```
|
||||
This will prompt you to perform a database backup before starting the migration
|
||||
process. Data loss is entirely possible otherwise.
|
||||
{: .code-aside}
|
||||
|
||||
### Docker Compose
|
||||
|
||||
If you are running Talk with docker-compose, you can use the following command
|
||||
to perform the migration:
|
||||
|
||||
```bash
|
||||
docker-compose run --rm talk cli migration run
|
||||
```
|
||||
This will prompt you to perform a database backup before starting the migration
|
||||
process. Data loss is entirely possible otherwise.
|
||||
{: .code-aside}
|
||||
|
||||
Reference in New Issue
Block a user