[Other doc versions]
[Doc downloads]
Hey! We're going to install Stash on Windows. There are a few steps, but we think you'll really like Stash once it's up and running.
For production environments, see also the additional steps at the end of this page.
Better check the Supported platforms page first; it lists the application servers, databases, operating systems, web browsers and JDKs that we have tested Stash with and recommend.
Atlassian only officially supports Stash running on x86 hardware and 64-bit derivatives of x86 hardware.
Cygwin Git is not supported. No internal testing is done on that platform, and many aspects of Stash's functionality (pull requests and forks among them) have known issues. When running Stash on Windows, always use msysGit.
In a command prompt, run this:
java -version
The version of Java should be 1.6.0 or higher.
Stash uses the JAVA_HOME environment variable to find Java. To check that, in a command prompt, run:
echo %JAVA_HOME%
You should see a path to the root directory of the Java installation. When running Stash on Windows, unlike Linux or Unix, JAVA_HOME
paths with spaces are just fine.
In a command prompt, run:
git --version perl --version
The version of Git should be 1.7.6 or higher. The version of Perl should be 5.8.8 or higher.
Download Stash from the Atlassian download site. Looking for the Stash WAR file?
Extract the downloaded file to an install location. The path to the extracted directory is referred to as the
in these instructions.<Stash installation directory>
Don't use spaces in the path to the Stash installation directory.
The Stash home directory is where your Stash data is stored.
Create your Stash home directory, and then tell Stash where you created it by setting a STASH_HOME
environment variable, as follows.
For Windows 7:
STASH_HOME
" as the Variable name, and the absolute path to your Stash home directory as the Variable value. Don't use a trailing backslash.There are a few things to know about setting up the Stash home directory on Windows that will make life easier:
<Stash installation directory>
— they should be entirely separate locations. If you do put the home directory in the <Stash installation directory>
it will be overwritten, and lost, when Stash gets upgraded. And, by the way, you can't use the same Stash home directory for multiple instances of Stash.The user that runs Stash should not have admin privileges (see this performance issue), but must have read, write and execute access to the Stash home directory and the <Stash installation directory>.
In a command prompt, change directory to the <Stash installation directory>
and run the following command:
bin\start-stash.bat
In your browser, go to http://localhost:7990 and run through the Setup Wizard. In the Setup Wizard:
Configure your email server so users can receive a link from Stash that lets them generate their own passwords. See Setting up your mail server.
Now is the time to set up your users in Stash, and to tell Stash about any existing repositories you have. Please the following pages for the details:
For production environments we recommend that you configure the additional aspects below. These are not necessary when installing for evaluation purposes. Please see Using Stash in the enterprise for more information about best practice.
In a command prompt, change directory to the <Stash installation directory>
and run:
bin\stop-stash.bat
To uninstall Stash, stop Stash as described above and then delete the <Stash installation directory
> and Stash home directory.