A comprehensive software solution aimed at providing the office workers with a stable and reliable piece of software fitting their daily workflow regardless of the level of IT competency.
Open the terminal and execute the following command to clone the repository:
git clone https://github.com/NikolaVetnic/Timelines Timelines && cd docker-compose
For local development set up the docker-compose/dev/.env following the docker-compose/.env.template file. The ASPNETCORE_ENVIRONMENT environment variable should be set to Development.
As for production, the setup is the same, save for the .env file path being docker-compose/prod.env, and the environment variable being set to Production.
The compose stack can be spun up from docker-compose using the ./dev/up.sh and ./prod/up.sh scripts. Teardown is possible via analogoues dn.sh scripts.
Frontend component as well as the API should be accessible on localhost at the designated port. API health can be checked by sending the GET /health request.
The services' port numbers are as follows:
| Service | Local Env | Docker Env | Within Docker |
|---|---|---|---|
| Core.Api | 25000 / 25051 |
26000 / 26061 |
8080 / 8081 |
| Core.Frontend | 23000 |
24000 |
23000 |
| Core.Db | 25432 |
25432 |
5432 |
ASP.NET Core ports are listed as HTTP / HTTPS for running application.
When Nginx is on, the components can be accessed as follows:
| Service | URL |
|---|---|
| Core.Api | localhost/api |
| Core.Frontend | localhost |