Skip to content

README.md

Latest commit

 

History

History
44 lines (35 loc) · 1.58 KB

README.md

File metadata and controls

44 lines (35 loc) · 1.58 KB

GridWars server project.

Build & deploy process

all paths are relative to project root directory. Require JDK 1.7, tomcat 7.x

  1. Use gradle wrapper script to install project dependencies in local maven repository. /core/gradlew install
  2. Use grails wrapper script to build .war file. /grailsw war
  3. Prepare folder structure for grailsw (see details below). Make sure, tomcat user has an rw access to it.
  4. Generated from grails javadoc and api-jar file should be set up in tomcat config as static content.
  5. Modify mailing service setup in Config file.
  6. 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.

Directory structure in GW_HOME.

/
  /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.)

Usage.

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)