• RunLog Website
• RunLog REST API

RunLog is an activity tracking application. Users can create/edit/delete activities. And activity has a start/stop button and while the activity is running, the device's geolocation coordinates are tracked and stored in the RunLog system.

The solution is comprised of 3 components:

1. RunLog.API is a REST API that allows for client applications to interact with the RunLog system. Provides data access and back-end processing.
2. RunLog.Web is a client-side SPA website to interface with the system.
3. RunLog Tests is a set of unit tests and integration tests to automate testing of the system components.

Additional components:

• LiteBulb.Database to store all the data used for the system.

#Tech Stack

1. .NET Core 3.1 (for Web API, Blazor WebAssembly and libraries)
2. .NET Standard 2.1 (for libraries)
3. LiteBulb MemoryDb 0.1 (for database)
4. Swagger (API documentation)
5. Serilog (logging)

The RunLog application needs a REST API to provide data storage and retrieval functionality. The API needs to perform some back-end processing. The API needs to write log messages to an AMQP message broker. An interactive UI is needed to provide user access to all the CRUD operations supported by the application.

A solution called RunLog will be developed to perform the required operations.

1. RunLog application needs a logical data model that includes two entities with a cardinality relationship of one-to-many.
2. REST API that implements all the CRUD operations using a resource-based modeling approach for each data model entity.
3. REST API requires HTTPS security.
4. Each invocation of the REST API should write a small log message describing the given interaction to an AMQP message broker.

Note: See below for links to code repositories.

• README.md
• Solution Document
• RunLog Rest API
• Diagrams
• Installation

• RunLog Project
• RunLog Repository

TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:

1. Installation process
2. Software dependencies
3. Latest releases
4. API references

• Build the solution in Visual Studio 2019 and run. TODO: Describe and show how to build your code and run the tests.

• RunLog Repository

If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files:

• ASP.NET Core
• Visual Studio Code
• Chakra Core