Skip to content

Commit

Permalink
docker instructions
Browse files Browse the repository at this point in the history
Updated instructions for docker use.
  • Loading branch information
leszczuu authored Sep 27, 2024
1 parent 9cd21f4 commit ceaee01
Showing 1 changed file with 16 additions and 1 deletion.
17 changes: 16 additions & 1 deletion doc/04-development.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,4 +65,19 @@ $ yarn watch

It's an infinite process, which will watch your changes in the assets folder and (re)build them. So all of your frontend changes should be done in `{root}/src/Resources/assets` directory. We have configured two independent entry points that should not be combined - `shop` for the storefront and `admin` for the admin panel.

> **⚠ Note**: Before every commit, you should type the `yarn dist` command from the plugin root directory to rebuild dist assets, which are located in `{root}/src/Resources/public`. <br> <br> You also shouldn't add assets to this folder manually because **they will be removed automatically**
> **⚠ Note**: Before every commit, you should type the `yarn dist` command from the plugin root directory to rebuild dist assets, which are located in `{root}/src/Resources/public`. <br> <br> You also shouldn't add assets to this folder manually because **they will be removed automatically**
#### Docker

To test plugin with docker You can use:

```bash
$ docker-compose up
$ docker-compose exec -it app composer install
$ docker-compose exec -it app yarn install
$ docker-compose exec -it -w /app/tests/Application app bin/console d:d:c
$ docker-compose exec -it -w /app/tests/Application app bin/console d:s:c
$ docker-compose exec -it -w /app/tests/Application app bin/console sy:fi:lo -q
```

This should make sure test app from docker container is up and running.

0 comments on commit ceaee01

Please sign in to comment.