A simple logbook application for pilots to log flights and for maintenance or repairs to be recorded per vehicle. Provides for a unified location for simulated and real flights to be logged.
Calculates detailed flight analytics broken down by aircraft type, conditions of flight, etc, which are displayed on the dashboard of the application.
Configuration supports display of user-desired columns in logbook as well as date and aircraft filtering,
- WebAPI
- Swagger endpoints
- CoreUI Angular Template
- CQRS pattern via MediatR
- JWT authentication
- Target dependency graph via Bullseye
- EFCore 5 interacting with MariaDB/MySQL
- Docker containerization
- xUnit integration tests
- i18n support for English, German and Japanese
- dotnet-format tool to enforce style
- OData for some queries
Along with the .NET 6.0 SDK, this project requires npm to be installed to install Angular assets.
If no environment variables are defined, an in-memory EFCore database is used with sample data seeded on application startup.
If an instance of MySQL or MariaDB is desired for the database:
- Run the db-dump SQL script in
./Databaseto instantiate the nisshi databse and create a user to connect with - Set the environment variable
ASPNETCORE_Nisshi_DatabaseProvidertomysql - Set the environment variable
ASPNETCORE_Nisshi_ConnectionStringtoserver=localhost;uid=nisshiuser;pwd=saishoNoYuuza1?;database=nisshi(modify the port/host as needed for your machine)
The project can be run locally from the dotnet CLI, using dotnet run -p ./src/Nisshi/Nisshi.csproj from the project root folder. Then open a web browser and navigate to https://localhost:5001/. Swagger endpoints are accessible by appending swagger to that URL.
Any changes to the Angular project in ./src/Nisshi/ClientApp will automatically reload the page.
This project has full Docker support and can be build and deployed by simply running docker-compose up -d from the project root directory.
If Docker is not desired, you can run dotnet run -p build/build.csproj from the project root directory to build the project, which will output the published artifacts in ./publish.
PRs and pushes/merges to master will trigger the GitHub build pipeline which runs a project-wide format check, and then builds and tests the project.