Skip to content

Commit

Permalink
VP-4928: Fix issues
Browse files Browse the repository at this point in the history
  • Loading branch information
mvktsk committed Sep 21, 2020
1 parent 3771e61 commit cee9b61
Show file tree
Hide file tree
Showing 3 changed files with 23 additions and 13 deletions.
1 change: 1 addition & 0 deletions DockerCompose/ModulesDevelop/docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ services:
- ${APP_DATA_MODULES}:/opt/virtocommerce/platform/App_Data/Modules
networks:
- virto
restart: unless-stopped

elastic:
image: docker.elastic.co/elasticsearch/elasticsearch:7.7.0
Expand Down
35 changes: 22 additions & 13 deletions docs/developer-guide/modules-development-via-docker.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ docker-compose -f docker-compose.yml up --build -d
6. [Create new module](./create-new-module.md) as described in the article
7. Write code for new module
8. Build new module
9. Connect new module with the platform
9. Copy built module to `Modules` folder
10. Debug new module

## Run Virto Commerce Platform Manager
Expand All @@ -86,19 +86,11 @@ Once the containers are started, open VC Platform Manager - http://localhost:809

![Choose sample data](../media/screen-sample-data.png)

## Connect new module with the platform
## Copy built module to Modules folder

Use symbolic link to connect newly created solution folder to the Platform ~/Modules:

* Run Command Prompt as an administrator.
* Navigate to the physical location folder of `./Modules` folder on host machine.
* Run the following command:

```cmd
mklink /d <your_module_name> <full_path_to_your_module_project>
```

* Restart Virto Commerce Platform after new module have been connected to the platform.
* Navigate to the `Modules` folder on local host
* Create folder for newly created module
* Copy `your_module_project.Web` folder to the created folder

## Debugging the module

Expand All @@ -118,12 +110,29 @@ mklink /d <your_module_name> <full_path_to_your_module_project>

![image](../media/attach_to_process_3.png)

If the new module has been rebuilt:

* Overwrite folder for newly created module by `your_module_project.Web`
* Restart the platform - click Setigns->Restart on Platform manager UI:

![Reststrt platform](../media/screen-restart-platform.png)

## Cleanup environment after debugging

When debugging process has finished, stop `docker-compose` by command:

```cmd
docker-compose down
```

Don't forget to delete newly created module from the `Modules` and `Modules\AppData` folders.

If you need to recreate platform database for next debug session, remove `db-volume` by command:

```cmd
docker volume rm db-volume
```

## How to

### Troubleshooting
Expand Down
Binary file added docs/media/screen-restart-platform.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit cee9b61

Please sign in to comment.