Commit 415dc979 authored by Reza Sahebgharan's avatar Reza Sahebgharan

docs(edit readme): edit readme.md

parent 437d73b1
Pipeline #637 passed with stages
in 8 seconds
...@@ -23,9 +23,10 @@ ...@@ -23,9 +23,10 @@
## Installation Guide ## Installation Guide
- create a folder in the production server for example in the drive C(ex: D:/build) - create a folder in the production server for example in the drive D(for example: D:/build)
* it is better to do not choose drive c
- navigate to created folder in previous step and create a file called docker-compose.yml (ex: D:/build/docker-compose.yml) - navigate to created folder in previous step and create a file called docker-compose.yml (for example: D:/build/docker-compose.yml)
- open docker-compose.yml with an editor and paste following statements in the created docker compose file - open docker-compose.yml with an editor and paste following statements in the created docker compose file
...@@ -60,9 +61,21 @@ networks: ...@@ -60,9 +61,21 @@ networks:
``` ```
- navigate to Drive D and create a folder called "data" - navigate to Drive D and create a folder called "data"
* it is better to do not choose drive c
- navigate to D:/data and create a folder called "db" - navigate to D:/data and create a folder called "db"
- if you choose drive other than drive D please edit above yaml file ***volumes*** section under ***mongo*** service:
for example if you choose drive E for creating folder "db" at previous step, change
```
volumes:
- D:\data\db:C:\data\db
```
into
```
volumes:
- E:\data\db:C:\data\db
```
- open CMD - open CMD
- CD to created folder in step 1 (ex: cd D:/build) - CD to created folder in step 1 (ex: cd D:/build)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment