You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This command will prompt you to confirm that you want to run it:
90
92
91
-
> WARNING! You are about to execute a migration in database "_<database-name>_" that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no) [yes]:
93
+
> WARNING! You are about to execute a migration in database "`<database>`" that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no) [yes]:
92
94
93
95
Hit `Enter` to confirm the operation.
94
96
95
97
#### Executing fixtures
96
98
97
-
> Fixtures are used to seed the database with initial values and must be executed after migrating the database.
99
+
Fixtures are used to seed the database with initial values and must be executed after migrating the database.
98
100
99
101
To list all the fixtures, run:
100
102
@@ -132,7 +134,7 @@ You can download/update all GeoLite2 databases at once, by running the following
132
134
php ./bin/cli.php geoip:synchronize
133
135
```
134
136
135
-
The output should be similar to the below, displaying per row:
137
+
The output should be similar to the below:
136
138
137
139
```shell
138
140
asn: n/a -> 2015-10-21 04:29:00
@@ -169,7 +171,7 @@ npm install
169
171
If the above command fails, it could be caused by user permissions of `npm`.
170
172
Recommendation is to install npm through `Node Version Manager`.
171
173
172
-
The watch command looks for JavaScript/CSS file changes and recompiles the assets under the public assets:
174
+
The **watch** command looks for JavaScript/CSS file changes and recompiles the assets under the public assets:
173
175
174
176
```shell
175
177
npm run watch
@@ -183,32 +185,30 @@ npm run prod
183
185
184
186
### Test the installation
185
187
186
-
> **Do not enable dev mode in production**
187
-
188
-
- Run the following command in your project's directory to start PHPs built-in server:
188
+
Run the following command in your project's directory to start PHPs built-in server:
189
189
190
190
```shell
191
191
php -S 0.0.0.0:8080 -t public
192
192
```
193
193
194
-
> Running command `composer serve` will do the same thing, but the server might get closed after a couple of minutes.
194
+
> Running command `composer serve` will do the same thing, but the server will time out after a couple of minutes.
195
195
196
-
> If you are still getting exceptions or errors regarding some missing services, try running the following command:
196
+
If you are still getting exceptions or errors regarding some missing services, try running the following command:
197
197
198
198
```shell
199
199
php ./bin/clear-config-cache.php
200
200
```
201
201
202
-
-Open a web browser and visit `http://localhost:8080/`
202
+
Open a web browser and visit `http://localhost:8080/`.
203
203
204
204
You should see the **Dotkernel Admin** login page.
205
205
If you ran the migrations you will have an admin user in the database with the following credentials:
206
206
207
-
-**User**: `admin`
207
+
-**Identity**: `admin`
208
208
-**Password**: `dotadmin`
209
209
210
210
> **Production only**: Make sure you modify the default admin credentials.
211
-
>
211
+
212
212
> **Development only**: `session.cookie_secure` does not work locally so make sure you modify your `local.php`, as per the following:
213
213
214
214
```php
@@ -219,4 +219,4 @@ If you ran the migrations you will have an admin user in the database with the f
219
219
];
220
220
```
221
221
222
-
> Do not change this in `local.php.dist` as well because this value should remain `true` on production.
222
+
> Do not change this in `local.php.dist` as well because this value must remain `true` on production.
0 commit comments