[Other doc versions]
This page provides information about running the Stash installer. For high-level information about installing and using Stash see Getting started.
On Linux and Windows systems, the installer can install Stash as a service.
A service account named 'atlstash' will be created.
init.d script will be linked to run levels 2, 3, 4 and 5. If you wish to change this, you will need to configure it manually.
The Linux installer file needs the executable flag set. Use this command:
chmod +x atlassian-stash-x.x.x-x64.bin
The installer generates a password for the service account. As a Windows administrator, you can update the account password if you wish to own the account. You'll also need to update the log on credentials for the service:
The 'atlstash' account will be configured with SeServiceLogonRight so that it can be used by the service. It will also be configured with
SeDenyRemoteInteractiveLogonRight so that it cannot be used to log into the machine.
For Windows services created using the Stash installer, the Stash home directory location (defined by the
STASH_HOME variable) is configured as a Tomcat Service JVM option. To change it see Change STASH_HOME when installed as a Windows service.
The Stash installer has three modes:
-cargument, the interaction with the user is performed in the terminal from which the installer was invoked.
-qargument, there is no interaction with the user and the installation is performed automatically with the default values.
Unattended mode also allows you to supply a response file with a
-varfile option, to supply answers for all questions that are used instead of the defaults. An example response file is:
On Mac OS X, mount the disk image, then run the Java stub in the installer using this command:
X.X.X is the version of Stash, and
-options can include
-varfile followed by the path to the response file.
For more information see the install4j documentation.