Community website for runners to share tracks and plan runs together.
|
|
2 jaren geleden | |
|---|---|---|
| config | 3 jaren geleden | |
| sandbox | 3 jaren geleden | |
| src | 2 jaren geleden | |
| .editorconfig | 3 jaren geleden | |
| .gitignore | 3 jaren geleden | |
| DESCRIPTION | 3 jaren geleden | |
| LICENSE | 3 jaren geleden | |
| README.md | 3 jaren geleden | |
| build.ps1 | 3 jaren geleden | |
| docker-compose-local.yml | 3 jaren geleden | |
| docker-compose-server.yml | 3 jaren geleden | |
| push.ps1 | 3 jaren geleden | |
| release.ps1 | 2 jaren geleden |
TODO
Start the client with
cd src/RunnersMeet.Client
ng serve
It will run on the Angular default port http://localhost:4200
Start the server by either launching it from within your IDE or by running
cd src/RunnersMeet.Server
dotnet run .
In development mode, the API server runs on https://localhost:7247 with Swagger enabled (https://localhost:7247/swagger)
./build.ps1
./push.ps1
To do some proper staging testing before updating the production environment, there is a dedicated docker-compose-local.yml file and a "sandbox" directory with HTTPS certificate and a mapped volume for the application data.
docker compose -f ./docker-compose-local.yml up
When running in this mode, the application frontend and backend are both accessed through https://localhost:7443
The docker-compose-server.yml file assumes that the container will be accessed through a reverse proxy like Nginx and that SSL is applied on the level of that proxy. The container runs over HTTP on port 80 which is exposed as 7180 on the host.
On the production server, the application directory looks something like this:
- (d) config # copied from this repository
- (f) app.prod.config.json
- (f) app.staging.config.json
- (d) data # mounted as "/app/data" in the container
- (d) files
- (f) tracks.db
- (f) tracks-log.db
- (f) docker-compose-server.yml # taken from this repository
The server can then be started with
docker compose -f ./docker-compose-server.yml up