Skip to content

Commit 4c75e17

Browse files
committed
Clarify database docs
1 parent c6c16bb commit 4c75e17

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

resources/views/docs/1/digging-deeper/databases.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,12 +55,10 @@ delete your user's data when they update your app.
5555

5656
### Running migrations
5757

58-
NativePHP will attempt to migrate your database on each boot-up.
58+
In production builds of your app, NativePHP will check to see if the app version has changed and attempt to migrate
59+
the user's copy of your database in their `appdata` folder.
5960

60-
You may also wish to manually migrate it during development. You can do this whether the application is running or not,
61-
but depending on how your app behaves, it may be better to do it before opening the app.
62-
63-
You can do this with the `native:migrate` command:
61+
During development, you will need to migrate your development database manually:
6462

6563
```shell
6664
php artisan native:migrate
@@ -69,6 +67,9 @@ php artisan native:migrate
6967
This command uses the exact same signature as the Laravel `migrate` command, so everything you're used to there can be
7068
used here.
7169

70+
You can do this whether the application is running or not, but depending on how your app behaves, it may be better to
71+
do it _before_ running your app.
72+
7273
### Refreshing your app database
7374

7475
You can completely refresh your app database using the `native:migrate:fresh` command:

0 commit comments

Comments
 (0)