zachjenkins/bingo_csharp-aspnetcore-mongodb

Bingo!

Bingo_csharp-aspnetcore-mongodb

Bingo!

NOTE -
***** The design used in this "service" is really only good for CRUD applications with very little complexity or business logic. *

***** This is meant to be a basic implemenation guide for Mongo, unit testing, integration testing, etc..

Bingo is a RESTful (not really though) API that provides data about fitness.. and fitness related.. stuff...

Tools Used

Mongo DB

Mongo DB C# Driver Library

ASP.NET Core

Deploying Bingo

The following things can be done in any order!

Starting Local Mongo Instance

Deploy MongoDB locally by running the following command in powershell:

From \Bingo_csharp-aspnetcore-mongodb\database >> `start-process start_db.bat`

Mongo will be hosted locally over port `27017` with a connection string of `mongodb//localhost:27017`

You may consider downloading a free MongoDB client from [RoboMongo](https://robomongo.org/)

Deploying API Locally

There are 2 ways to deploy the API:

1. Deploy from visual studio under the *debug* menu.
1. Deploy from command-line using dotnet core build tools

From the directory .\Bingo_csharp-aspnetcore-mongodb\src\Bingo.Api >> `dotnet run`

Running Unit and Integration Tests

**Mongo does not need to be deployed for this to work. Neither does ASP.NET. Pretty much nothing does.**

1. Run them in Visual Studio!
1. If you do not have VS, run tests from command-line with the following:

From the root of the project >> `dotnet test`

Framework dependencies such as mongoDb and ASP.NET core are initialized in-memory or managed entirely by the test harness, for the lifetime of the test execution. No setup required. -- CORRECTION - This implementation is not actually deploying Mongo in-memory, but instead the test harness is just managing the mongo binaries.. .. ..

bingo_csharp-aspnetcore-mongodb's Issues

Mongo2Go Server remains open after test run

Mongo Server process remains open after test run.

Need to figure out a way to do this during the shared context Dispose.

Current MongoDbRunner.Dispose() method not working as expected. Needs investigation.

API does not self-manage mongoDb and data.

if you deploy using an executable/dll file, the API should seed it's own data on startup, rather than relying on a data script external to the application.

Swagger page not rendering

Create "Region" model

Connects to muscles and groups models

Create "Group" model

Links to muscles and regions models