all paths are relative to project root directory. Require JDK 1.7, tomcat 7.x
- Use gradle wrapper script to install project dependencies in local maven repository.
/core/gradlew install - Use grails wrapper script to build .war file.
/grailsw war - Prepare folder structure for grailsw (see details below). Make sure, tomcat user has an rw access to it.
- Generated from grails javadoc and api-jar file should be set up in tomcat config as static content.
- Modify mailing service setup in Config file.
- Deploy war file in tomcat. Note, that you need to have environmental variable called GW_HOME to prepared directory structure. It'll be printed on grails startup, and server will die, if var is not specified.
/
/db (created automatically)
/player-jars (specified in configs)
/player-matches (specified in configs)
/player-outputs (specified in configs)
/workers (specified in configs)
/workerClassPath (specified in configs. Contents of that dir are created by gradle task createWorkerClassPath.)
config.groovy (put file from repository here.)
Admin controller have a nice overview of all available controllers.
For monitoring use:
/admin/queue
/admin/histo
For final match use
/admin/clear and /admin/startFight controllers.
You can update most config values from admin page.
Default admin accounts are: login: admin , pass: admin login: admin2, pass: admin
Passwords can be changed from user controller.
Enjoy)