Developing locally

Nobody has claimed this yet.

I am reading through https://github.com/linkedin/dr-elephant/wiki/Developer-Guide#local-deployment-of-dr-elephant-for-testing

The steps outlined to have a local instance running for development include "deploying locally" by generating a dist package and unzipping it. I think this is quite a lengthy and cumbersome process especially for new contributors who are trying to get familiar with the code and have quick feedback.

The project is a Play application which comes with an "auto-reload" feature, I've been looking at making `activator run`, `sbt run` or `play run` work, (work in progress so far)

Have other contributors made the same observations ? Is there a historic / contextual reason I'm missing for this process not being de-facto for dr-elephant ?

Start with the Developer Guide's local deployment section and compare its dist-package workflow with the proposed activator run, sbt run, and play run commands. Check whether the Play application's auto-reload mode can support local development; done means contributors can start a local instance with quick feedback without manually generating and unzipping a dist package.

Written by the indexing model from the issue text.