You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.

Start/Stop Scripts

If you built Structr from the sources and start it from the main directory, the following start/stop scripts are available:

start [name] [heapsize]

Start the Structr instance.

Takes two optional parameters to set the JVM heap size (in GB) and a name.

The start script is a wrapper around the run.sh script (see below) to set the environment variables for name, heap size, base directory and the path of the run script.
stop [name]

Stop the currently running Structr instance.

Takes an optional parameter to stop the instance started with the given name.

The stop script looks for a pid file to get the process id of the Structr instance.

It monitors the log file and will return successfully once "Shutdown complete" is detected in the log.
run.sh [name] [heapsize]

Run the Structr JVM process.

Takes two optional parameters to set the JVM heap size (in GB) and a name.

The run.sh script sets the neccessary environment variables for name, heap size, pathes of the run script, logfile, pidfile and config file and starts a new JVM process with Structr's main server class.

It monitors the log file and will return successfully once "Initialization complete" is detected in the log.

The JVM process is run in the background using nohup.

Search results for "Start/Stop Scripts"

We could not find anything matching "Start/Stop Scripts" in our documentation. Please rephrase your search.

You can also ask your questions in the Structr Google Group or create a free account in the Structr Support Portal.
Click here to send feedback to the Structr team.