Running the Galos software:
Dependencies: Java 8 or later needs to be installed first. Oracle JVM gives better performance and has been more tested, but OpenJDK is also supported.
Execute the run.sh or start.sh script if using Linux or BSD, run.bat if using Windows, or run.command if using Mac.
On Unix, the run.sh script must be run from within the installation directory, and uses this directory to search for configuration files, store logs, and for the nxt_db blockchain database. The start.sh script can be run from any directory, it starts the java process in the background and uses ~/.nxt for configuration files, logs, and the nxt_db database. Unlike run.sh, start.sh uses desktop mode, creating a desktop tray icon and opening the JavaFX UI if supported.
The initialization takes a few seconds. When it is ready, you should see the message "Galo Server 1.x.x started successfully" in the console log. If run in desktop mode, a JavaFX window will open automatically. Otherwise, open a browser, without stopping the java process, and go to http://localhost:7876 , where the Galo UI should now be available.
To stop the application, type Ctrl-C inside the console window, or use the stop.sh script if started with start.sh.
Warning: It is better to use only latin characters and no spaces in the path to the Galo installation directory, as the use of special characters may result in permissions denied error in the browser, which is a known jetty issue.
There are many configuration parameters that could be changed, but the defaults are set so that normally you can run the program immediately after unpacking, without any additional configuration. To see what options are there, open the conf/nxt-default.properties file. All possible settings are listed, with detailed explanation. If you decide to change any setting, do not edit nxt-default.properties directly, but create a new conf/nxt.properties file and only add to it the properties that need to be different from the default values. You do not need to delete the defaults from nxt-default.properties, the settings in nxt.properties override those in nxt-default.properties. This way, when upgrading the software, you can safely overwrite nxt-default.properties with the updated file from the new package, while your customizations remain safe in the nxt.properties file.
The java process communicates with peers on port 47874 tcp by default. If you are behind a router or a firewall and want to have your node accept incoming peer connections, you should setup port forwarding. The server will still work though even if only outgoing connections are allowed, so opening this port is optional.
The user interface is available on port 7876. This port also accepts http API requests which other Galo client applications could use.
The blockchain is stored on disk using the H2 embedded database, inside the nxt_db directory. When upgrading, you should not delete the old nxt_db directory, upgrades always include code that can upgrade old database files to the new version whenever needed. But there is no harm if you do delete the nxt_db, except that it will take some extra time to download the blockchain from scratch.
The default Galo client does not store any wallet-type file on disk. Unlike bitcoin, your password is the only thing you need to get access to your account, and is the only piece of data you need to backup or remember. This also means that anybody can get access to your account with only your password - so make sure it is long and random. A weak password will result in your funds being stolen immediately.
The java process logs its activities and error messages to the standard output which you see in the console window, but also to a file nxt.log, which gets overwritten at restart. In case of an error, the nxt.log file may contain helpful information, so include its contents when submitting a bug report.
The source is included in the src subdirectory. To compile it on unix, just run the enclosed compile.sh script. This will compile all java classes and put them under the classes subdirectory, which is already in the classpath used by the run.sh startup script. The compiled class files can optionally be packaged in a gal.jar file using the enclosed jar.sh script, and then gal.jar should be included in the classpath instead of the classes subdirectory.