Fix up some things with docker to hopefully resolve prod issues

[timhaley94]

Background

The server isn't running correctly in prod. Current theory is that because the start script for server was using pm2, which starts a background process, the container immediately dies. At least this is what happened when I pulled the latest server image locally. Additionally, we don't need pm2 because there are beanstalk settings that will restart containers when the die.

Proposed Changes

Technical changes:

• No pm2 or start.sh for server
• Rearrange docker-compose.yml so that server ports are not exposed
• Fix typo in client config

Future work

What will we need to do later:

• Make sure that new server image works as expected
• Make sure that server containers actually start
• Add beanstalk settings to automatically restart stopped containers

[codeclimate[bot]]

Code Climate has analyzed commit b751d20c and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 25.4% (0.0% change).

View more on Code Climate.