I expect you are quite familiar with docker and environments, so you know what to do when using Marvin and so I will leave the obviously configuration required for your own purpose totally up to you.
Marvin provides some microservice endpoints. Just start Marvin by launching 🚀 his container in your desired environment. He will expect you talking to him via port 8042 (yes you guessed absolutely right, he might probably listen on the Heart of Gold by now - special thanks to Douglas Adams!)
HTTP-Get Endpoints | Description |
---|---|
/api/check/howareyou | Marvin answers via http body and status code, so you can integrate this as a container healthcheck for your environment. http-200 - I'm happy that you ask, I'm feeling well. http-429 - I'm so depressed because after hearing this protocol again and again, you will want to replace me. |
/api/cmd/initiateProtocol/<x> | x=88 - just be happy and work with no complaints x=100 - be unhappy, claim to work to much x=9 - play death don't answer anymore on healthchecks. x=-1 - dissolve Marvin! (i.e. corresponding instance will stop to exists) x=53 - Show your IP Address. |
This should be enough for the most experiments. As you clone Marvin to scale in some cluster environments, he will pick up a random number between 1 and 1000 as ID, and place it in his answers. So you have a change to see which instance answers.
You read it till the end, so it was not just TL;DR and you may find Marvin useful. Let Marvin and me know on GitHub if he was useful or if you miss something.
Have fun!
Stefan & Marvin ;-)