You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update README and configuration scripts to reflect branch name changes and improve package versioning
- Enhanced README.md with formatting improvements and clarified sections.
- Updated GitHub Actions workflow to use 'main' branch instead of 'master'.
- Modified build and packaging scripts to align with the new branch naming convention.
- Changed package references in Orders.WebApi.csproj to use version wildcards for better flexibility.
This repo contains a set of libraries to build LOB (Line Of Business) applications. The library is open source and built to be PRODUCTION READY. The library is built on top of .NET9, it is designed and maintained by Genocs.
47
+
This repo contains a set of libraries to build LOB (Line Of Business) applications. The library is open source and built to be PRODUCTION READY. The library is built on top of .NET9, it is designed and maintained by Genocs.
49
48
50
49
Packages are available on [NuGet Genocs](https://www.nuget.org/profiles/gioema_nocco).
51
50
52
51
## The idea
53
52
54
-
***Build a software library to be cloud agnostic***
53
+
**_Build a software library to be cloud agnostic_**
55
54
56
-
Building a software library to be cloud agnostic has several advantages. First, it allows developers to create applications that can be deployed on any cloud platform without having to rewrite code or make major changes. This makes it easier for developers to quickly deploy their applications across multiple cloud providers. Additionally, it reduces the cost of development and maintenance since developers don’t have to write separate code for each cloud provider. Finally, it increases the scalability of applications since they can be easily deployed on different cloud platforms with minimal effort.
55
+
Building a software library to be cloud agnostic has several advantages. First, it allows developers to create applications that can be deployed on any cloud platform without having to rewrite code or make major changes. This makes it easier for developers to quickly deploy their applications across multiple cloud providers. Additionally, it reduces the cost of development and maintenance since developers don’t have to write separate code for each cloud provider. Finally, it increases the scalability of applications since they can be easily deployed on different cloud platforms with minimal effort.
57
56
58
-
***Cloud agnostic by use of Containers***
57
+
**_Cloud agnostic by use of Containers_**
59
58
60
59
The advantages of using containers are numerous. Containers provide a lightweight, portable, and isolated environment for applications to run in, allowing them to be easily moved between different systems. This makes it easier to deploy applications quickly and reliably across different environments. Additionally, containers can help reduce resource consumption by running multiple applications on the same host, as each container is isolated from the others. This helps to improve efficiency and scalability. Finally, containers provide an additional layer of security, as they are isolated from the underlying operating system and other applications.
61
60
62
61
## Documentation
63
62
64
-
You can find a useful documentation about how to use the library. The documentation contains the complete set of libraries, template, CLI that altogether make the *genocs ecosystem* a comprensive set of tools to build enterprise solutions.
63
+
You can find a useful documentation about how to use the library. The documentation contains the complete set of libraries, template, CLI that altogether make the _genocs ecosystem_ a comprensive set of tools to build enterprise solutions.
65
64
66
65
Documentation available at [Genocs Blog](https://genocs-blog.netlify.app/library/)
67
66
@@ -70,8 +69,7 @@ Documentation available at [Genocs Blog](https://genocs-blog.netlify.app/library
70
69
In this section you can find the infrastructure components you need to execute the solution. Infrastucture components are the database, the enterprice servise bus, the distributed logging, monitoring, tracing systems along with database and many more.
71
70
You can use **Docker compose** to setup the infrastructure components just by running few commands.
`infrastructure-scaling.yml` allows to install the scaling infrastructure components composed by a Fabio (Loadbalancer) Service Discovery (Consul) components. They are:
143
+
146
144
-[Fabio](https://fabiolb.net/)
147
145
-[Consul](https://www.consul.io/)
148
146
149
-
150
147
`infrastructure-security.yml` allows to install the security infrastructure components.
151
148
152
149
Inside the file you can find:
@@ -158,9 +155,8 @@ Inside the file you can find:
158
155
> The commands above allows to setup infrastructure components, this means you can find all the containers inside the same network `genocs`.
159
156
>
160
157
> Whenever possible the data are persisted on the host machine by means of volumens, so you can restart the containers without losing data.
161
-
162
158
163
-
```yml
159
+
```yml
164
160
networks:
165
161
genocs:
166
162
name: genocs-network
@@ -185,26 +181,24 @@ volumes:
185
181
186
182
Remember to add the network configuration inside your docker compose file to setup the network, before running the containers.
187
183
188
-
189
-
## ***Kubernetes cluster***
184
+
## **_Kubernetes cluster_**
190
185
191
186
You can setup the application inside a Kubernetes cluster.
192
187
193
-
Check the repo [enterprise-containers](https://github.com/Genocs/enterprise-containers) to setup a Kubernetes cluster.
188
+
Check the repo [enterprise-containers](https://github.com/Genocs/enterprise-containers) to setup a Kubernetes cluster.
194
189
There you can find scripts, configuration files and documentation to setup a cluster from scratch.
195
190
196
-
## ***Aspire Integration***
191
+
## **_Aspire Integration_**
197
192
198
193
SOON :rocket:
199
194
200
-
201
195
## Support
202
196
203
-
Use [**api-workbench**](./api-workbench.rest) inside Visual Studio code with [REST Client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) plugin
197
+
Use [**api-workbench**](./api-workbench.rest) inside Visual Studio code with [REST Client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) plugin
204
198
205
199
## Configuration
206
200
207
-
```json
201
+
```json
208
202
"app": {
209
203
"name": "Demo WebApi",
210
204
"service": "demo-service",
@@ -432,15 +426,17 @@ Use [**api-workbench**](./api-workbench.rest) inside Visual Studio code with [RE
432
426
}
433
427
}
434
428
```
429
+
435
430
---
436
431
437
432
## Demo Application
438
-
Inside the library there is a simple demo application you can use to test the library.
433
+
434
+
Inside the library there is a simple demo application you can use to test the library.
439
435
440
436
Following are the commands to build and run the demo application.
441
437
442
-
```bash
443
-
# Build the solution
438
+
```bash
439
+
# Build the solution
444
440
dotnet build
445
441
446
442
# Pack the projects
@@ -451,7 +447,7 @@ dotnet run --project ./src/Genocs.Core.Demo.WebApi
451
447
dotnet run --project ./src/Genocs.Core.Demo.Worker
0 commit comments