Skip to main content

Run Daikoku

Now you are ready to run Daikoku. You can run the following command with some tweaks, depending on the way you want to configure Daikoku. If you want to pass a custom configuration file, use the -Dconfig.file=/path/to/file.conf option in the following commands.

warning

Daikoku needs a database to run. Before run it, think to start your Postgres instance and setup a database with the right name (cf. configuration)

 unzip daikoku-x.x.x.zip
cd daikoku
./bin/daikoku

Run examples

$ java \
-Xms2G \
-Xmx8G \
-Dhttp.port=8080 \
-Ddaikoku.init.data.from=/home/user/daikoku.ndjson \
-Dconfig.file=/home/user/daikoku.conf \
-jar ./daikoku.jar

[info] play.api.Play - Application started (Prod)
[warn] daikokuEnv - Main dataStore seems to be empty, importing from /home/user/daikoku.conf ...
[warn] daikokuEnv - Importing from: /home/user/daikoku.ndjson
[info] p.c.s.AkkaHttpServer - Listening for HTTP on /0:0:0:0:0:0:0:0:8080

If you choose to start Daikoku without importing existing data, Daikoku will create a new admin user and print the login details in the log.

$ java \
-Xms2G \
-Xmx8G \
-Dhttp.port=8080 \
-jar daikoku.jar

[info] play.api.Play - Application started (Prod)
[warn] DaikokuEnv - Main dataStore seems to be empty, generating initial data ...
[info] p.c.s.AkkaHttpServer - Listening for HTTP on /0.0.0.0:8080
[warn] DaikokuEnv -
[warn] DaikokuEnv - You can log in with admin@daikoku.io / wr4pHmVRArCGhHoteMfwqV6UuvQh6J2z
[warn] DaikokuEnv -
[warn] DaikokuEnv - Please avoid using the default tenant for anything else than configuring Daikoku
[warn] DaikokuEnv -