Updating instructions

[SCdF]

Reworking our easy deployment section to make it even easier
(hopefully), by adding GUI instructions (kitematic) and a
docker-compose file for CLI, for folks who don't want to do core
development and instead are just checking out the reference app or are
developing configurations of their own.

Moved the Supported Browsers section up as it's not realy anything to do
with development setup, and should really be known by everyone.

[SCdF]

@abbyad let me know if this is what you were thinking

[Hareet]

@SCdF
Kitematic has a few constraints that are making our setup more complicated than simply clicking on our image.

Kitematic issues:

• In order to create a custom docker network, which our setup requires to run, you have to open up a CLI terminal inside Kitematic and paste docker commands.
• Same as above to create docker volumes and connect them to our two containers
• Run haproxy container after medic-os

Kitematic process would be:

• Launch Kitematic
• Search "Medic Mobile" or "Medic OS"
• Download image
• Open terminal, run:
• docker create network medic-net
• docker create volume medic-data
• Launch Medic-OS
• configure it to use network and volume
• configure environment variables
• Launch HAproxy
• configure it use network and volume
• configure environment variables

In my opinion, I feel it's easier to ask the user to copy/paste the compose file, open a terminal once and run:

• export variables
• docker-compose up

Basically, all of the definitions found in our docker-compose yaml have to be manually recreated in terminal or configured after the user launches the image from Kitematic.

Previously, I was attempting to make the image have entrypoint scripts that could bootstrap around the kitematic constraints. I can revisit that idea if you think its best, but that won't be ready for CHT release.

Can we only highlight the compose method for now/release and hop on a call to discuss if Kitematic should be our future?

[abbyad]

Overall I think the content is helpful. There are places we may need to change the tone based on the type of guide it is, and update some CHT language for consistency. I think @CescaGarrett can help with that aspect.

Also, I think that the README is getting too large and the Dev Setup Tests and Automated Deployment on Travis should be moved to a separate file focused on setup for those contributing to the Core Framework itself.

[abbyad]

Nice work, overall I think this structure is much clearer!

The INSTALL file could use some sub headers, and other than that it's mostly minor changes or areas that could be made more concise.

[abbyad]

Looks great, nice work @SCdF!

No need to hold this back any longer. It reads cleanly now and we can continue to improve over time as needed.