datahub/wherehows-backend/runBackend

set -a
source application.env
set +a

export JAVA_OPTS="-Xms512m -Xmx2048m -Dhttp.port=19001"

build/stage/wherehows-backend/bin/playBinary
Update runBackend to source application.env for conf values (#458) 2017-04-26 16:34:50 -07:00			`set -a`
			`source application.env`
			`set +a`

			`export JAVA_OPTS="-Xms512m -Xmx2048m -Dhttp.port=19001"`

Replace sbt build with native Gradle Play plugin and update the docs. (#352) Benefits 1. Simpler setup - no need to download activator in order to build & run 2. Faster build - See https://engineering.linkedin.com/play/developing-play-applications-using-gradle 3. Streamlined dependency management - Everything defined in build.gradle, instead of build.gradle + build.sbt 4. Better integration with gradle lifecycle tasks - build, test, dist, clean all work as expected Changes 1. Location of staging & distribution files moved from target to build 2. Use ./gradle -t runPlayBinary to run app with hot reload support 3. The generated start scripts are quite different from those generated by sbt 2017-03-21 11:37:38 -07:00			`build/stage/wherehows-backend/bin/playBinary`