Merge pull request #14 from meysamhadeli/feature/add-dotnet-tools-con…

…figurations feat: Add dotnet tools configurations.
meysamhadeli · Aug 22, 2024 · a0e372e · a0e372e
2 parents c5faa82 + 5a125bd
commit a0e372e
Show file tree

Hide file tree

Showing 3 changed files with 75 additions and 48 deletions.
diff --git a/.config/dotnet-tools.json b/.config/dotnet-tools.json
@@ -0,0 +1,20 @@
+{
+  "version": 1,
+  "isRoot": true,
+  "tools": {
+    "dotnet-outdated-tool": {
+      "version": "4.6.4",
+      "commands": [
+        "dotnet-outdated"
+      ],
+      "rollForward": false
+    },
+    "dotnet-ef": {
+      "version": "8.0.8",
+      "commands": [
+        "dotnet-ef"
+      ],
+      "rollForward": false
+    }
+  }
+}
diff --git a/README.md b/README.md
@@ -20,6 +20,8 @@
 - [The Domain and Bounded Context - Service Boundary](#the-domain-and-bounded-context---service-boundary)
 - [Structure of Project](#structure-of-project)
 - [Prerequisites](#prerequisites)
+- [Development Setup](#development-setup)
+  - [Dotnet Tools Packages](#dotnet-tools-packages)
 - [How to Run](#how-to-run)
   - [Config Certificate](#config-certificate)
   - [Docker Compose](#docker-compose)
@@ -133,6 +135,18 @@ I used CQRS to decompose my features into small parts that makes our application
 
 Using the CQRS pattern, we cut each business functionality into vertical slices, for each of these slices we group classes (see [technical folders structure](http://www.kamilgrzybek.com/design/feature-folders)) specific to that feature together (command, handlers, infrastructure, repository, controllers, etc). In our CQRS pattern each command/query handler is a separate slice. This is where you can reduce coupling between layers. Each handler can be a separated code unit, even copy/pasted. Thanks to that, we can tune down the specific method to not follow general conventions (e.g. use custom SQL query or even different storage). In a traditional layered architecture, when we change the core generic mechanism in one layer, it can impact all methods.
 
+## Development Setup
+
+### Dotnet Tools Packages
+For installing our requirement package with .NET cli tools, we need to install `dotnet tool manifest`.
+```bash
+dotnet new tool-manifest
+```
+And after that we can restore our dotnet tools packages with .NET cli tools from `.config` folder and `dotnet-tools.json` file.
+```
+dotnet tool restore
+```
+
 ## How to Run
 
 ### Config Certificate

diff --git a/deployments/docker-compose/infrastracture.yaml b/deployments/docker-compose/infrastracture.yaml
@@ -39,30 +39,28 @@ services:
     #######################################################
     #  EventStoreDB
     #######################################################
-  eventstore.db:
-      image: eventstore/eventstore:21.2.0-buster-slim
-      restart: on-failure
-      environment:
-          - EVENTSTORE_CLUSTER_SIZE=1
-          - EVENTSTORE_RUN_PROJECTIONS=All
-          - EVENTSTORE_START_STANDARD_PROJECTIONS=true
-          - EVENTSTORE_EXT_TCP_PORT=1010
-          - EVENTSTORE_EXT_HTTP_PORT=2113
-          - EVENTSTORE_INSECURE=true
-          - EVENTSTORE_ENABLE_EXTERNAL_TCP=true
-          - EVENTSTORE_ENABLE_ATOM_PUB_OVER_HTTP=true
-      ports:
-          - '1010:1113'
-          - '2113:2113'
-      networks:
-          - booking
+  eventstore:
+    container_name: eventstore
+    image: eventstore/eventstore:latest
+    restart: unless-stopped
+    environment:
+      - EVENTSTORE_CLUSTER_SIZE=1
+      - EVENTSTORE_RUN_PROJECTIONS=All
+      - EVENTSTORE_START_STANDARD_PROJECTIONS=True
+      - EVENTSTORE_HTTP_PORT=2113
+      - EVENTSTORE_INSECURE=True
+      - EVENTSTORE_ENABLE_ATOM_PUB_OVER_HTTP=True
+    ports:
+      - "2113:2113"
+    networks:
+      - booking
 
 
     #######################################################
     #  Mongo
     #######################################################
   mongo:
-    image: mongo
+    image: mongo:latest
     container_name: mongo
     restart: unless-stopped
     # environment:
@@ -72,51 +70,46 @@ services:
       - booking
     ports:
       - 27017:27017
-    volumes:
-      - mongo:/data/db
 
 
     #######################################################
     #  Elastic Search
     #######################################################
   elasticsearch:
-   container_name: elasticsearch
-   image: elasticsearch:7.17.9
-   restart: unless-stopped
-   ports:
-    - 9200:9200
-   volumes:
-    - elasticsearch-data:/usr/share/elasticsearch/data
-   environment:
-    - xpack.monitoring.enabled=true
-    - xpack.watcher.enabled=false
-    - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
-    - discovery.type=single-node
-   networks:
-    - booking
+    container_name: elasticsearch
+    image: elasticsearch:7.17.9
+    restart: unless-stopped
+    ports:
+      - 9200:9200
+    volumes:
+      - elasticsearch-data:/usr/share/elasticsearch/data
+    environment:
+      - xpack.monitoring.enabled=true
+      - xpack.watcher.enabled=false
+      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
+      - discovery.type=single-node
+    networks:
+      - booking
 
     #######################################################
     #  Kibana
     #######################################################
   kibana:
-   container_name: kibana
-   image: kibana:7.17.9
-   restart: unless-stopped
-   ports:
-    - 5601:5601
-   depends_on:
-    - elasticsearch
-   environment:
-    - ELASTICSEARCH_URL=http://localhost:9200
-   networks:
-    - booking
+    container_name: kibana
+    image: kibana:7.17.9
+    restart: unless-stopped
+    ports:
+      - 5601:5601
+    depends_on:
+      - elasticsearch
+    environment:
+      - ELASTICSEARCH_URL=http://localhost:9200
+    networks:
+      - booking
 
 
-
 networks:
   booking:
-    name: booking
-
 
 volumes:
   elasticsearch-data: