Running the Stash installer

Redirection notice

This page will redirect to /display/BitbucketServer/Running+the+Bitbucket+Server+installer .

This page provides information about running the Stash installer. For high-level information about installing and using Stash see Getting started.

Installers are available for Linux, Mac OS X and Windows operating systems. 

The installer will:

  • Install Stash into a fresh directory, even if you have an earlier version of Stash installed.
  • Install a supported version of the Java JRE, which is only available to Stash, if necessary.
  • Launch Stash when it finishes.

Additional services provided by the installer, and described on this page, are:

Note that you can also automate the Stash Setup Wizard so that a Stash instance can be completely provisioned automatically – see Automated setup for Stash.

Running the installer

Download the Stash installer from the Atlassian download site.

On Linux, you need to set the executable flag on the installer file before running it: 

chmod +x atlassian-stash-x.x.x-x64.bin

Run the installer, and follow the installation wizard:

Install Stash as a service

On Linux and Windows systems, the installer can install Stash as a service (although not when upgrading an existing instance of Stash).

A service account named 'atlstash' will be created.

On Linux

  • The 'atlstash' account will be a locked account (it cannot be used to log in to the system). 

  • The 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.

On Windows

  • 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 SeDenyBatchLogonRight, SeDenyInteractiveLogonRight, SeDenyNetworkLogonRight, and 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.

Console and unattended mode

The Stash installer has three modes:

  • GUI mode: the default mode for the installer is to display a GUI installer.
  • Console mode: if the installer is invoked with the -c argument, the interaction with the user is performed in the terminal from which the installer was invoked.
  • Unattended mode: if the installer is invoked with the -q argument, 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:

Example response file
 // Should Stash be installed as a Service? Must be ADMIN (default: true if the process is running with administrator rights, false otherwise). If false, the home and installation directories must be specified to point to directories owned by the user
app.install.service$Boolean=true

// The ports Stash should bind to (defaults: portChoice=default, httpPort=7990, serverPort=8006)
portChoice=custom
httpPort=7990
serverPort=8006


// Path to the Stash HOME directory (default: /var/atlassian/application-data/stash if the process is running with administrator rights, ~/atlassian/application-data/stash otherwise)
app.stashHome=/var/atlassian/application-data/stash


// The target installation directory (default: /opt/atlassian/stash/<VERSION> if the process is running with administrator rights, ~/atlassian/stash/<VERSION> otherwise)
app.defaultInstallDir=/opt/atlassian/stash/<VERSION>

On Windows, you must tell CMD/PowerShell to wait for the install4j process to use console/unattended mode:

start /wait installer.exe -c

On Mac OS X, mount the disk image, then run the Java stub in the installer using this command:

/Volumes/Stash/Stash\ X.X.X\Installer.app/Contents/MacOS/JavaApplicationStub -options

where X.X.X is the version of Stash, and -options can include -c or -q, and -varfile followed by the path to the response file.

For more information see the install4j documentation.

Further reading

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport