From ceaee016cc739f3916523f0aeb8684051166a5bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mateusz=20Deszert-K=C5=82osowski?= Date: Fri, 27 Sep 2024 09:46:02 +0200 Subject: [PATCH] docker instructions Updated instructions for docker use. --- doc/04-development.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/doc/04-development.md b/doc/04-development.md index 8a83b71c..d0a57fa3 100644 --- a/doc/04-development.md +++ b/doc/04-development.md @@ -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`.

You also shouldn't add assets to this folder manually because **they will be removed automatically** \ No newline at end of file +> **⚠ 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`.

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.