App Premise

3 endpoints on the API:

1. GET /api/redis
   this retrieves the values in a test key within redis
2. POST /api/redis
   this increments the counter against that key
3. DELETE /api/redis
   this removes the key so that you can reset

Testing incrementing the key in redis can be achieved with the following command line loop.

while true; do curl --insecure -d '{}' -H "Content-Type: application/json" -X POST http://localhost:5001/api/redis; sleep 1; done

(change this to http if running in the container)

This will fire off POST requests to thew endpoint, which should allow you to see the key incrementing at the GET endpoint above.

To reset the value in redis, run:

curl --insecure -X DELETE https://localhost:5001/api/redis

(change this to http if running in the container)

Running the app - Docker

docker-compose up --build

That's it - it should startup the redis API on http://localhost:5001/api/redis and will point at a redis container within docker with a name simple-api-redis.

It relies upon appsettings to work out whether it's running in dev or prod to evaluate whether it points at localhost or simple-api-redis as host for the redis instance.

Local Development

Setting up Redis in a container for local development

Run the docker container with redis in it.

docker run --name k8s-first-play-redis -p 6379:6379 -d redis

(if you already run redis locally, you will need to expose it under a different port)

Ensure you can connect to it:

• Via commandline: redis-cli
• Via docker: docker run -it --link k8s-first-play-redis:redis --rm redis redis-cli -h redis -p 6379

If you feel you want to validate the above two connections are the same just run set test 1 in one, ensure you can get test in it before exiting, then connect to the other and run get test - you should find the value there as it's the same running instance of redis.

Running the App Locally

Startup the app with dotnet run within the dotnet project folder, and you can hit: https://localhost:5001/api/redis with an HTTP GET.