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.
At the time of writing, on Mac OS X, the Git tar archive can fail on special characters when using SSH to secure connections between your computer and Stash. (The Git archive command allows you to download as a single file the files in a checkout of the Git repository.) We recommend that you use the zip format; you can set that using the following command:
git archive --format zip
Download and install the latest stable Perl release from http://www.perl.org/get.html, or use your favourite package manager.
Now try running 'perl --version' again. The version of Perl should be 5.8.8 or higher.
Extract the downloaded file to an install location. The path to the extracted directory is referred to as the<Stash installation directory> in these instructions.
5. Tell Stash where to store your data
The Stash home directory is where your Stash data is stored.
Create your Stash home directory (without spaces in the name), and then tell Stash where you created it by editing the <Stash installation directory>/bin/setenv.sh file – uncomment the STASH_HOME line and add the absolute path to your home directory. Here's an example of what that could look like when you're done:
You should not locate your Stash home directory inside the <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'll need separate Stash home directories if you want to run multiple instances of Stash.
6. Start Stash!
In a terminal, change directory to <Stash installation directory> and run this:
bin/start-stash.sh
In your browser, go to http://localhost:7990 and run through the Setup Wizard. In the Setup Wizard:
Select Internal at the 'Database' step, if you are evaluating Stash. Stash will happily use its internal database, and you can easily migrate to external database later. See Connecting Stash to an external database.
For production or enterprise 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.
For production environments the Stash home directory (created in step 7 above) should be secured against unauthorised access. See Stash home directory.
Stash を HTTPS で保護する
For production environments access to Stash should be secured using HTTP over SSL, especially if your data is sensitive and Stash is exposed to the internet. See Securing Stash with HTTPS.
Where you are running Stash behind a proxy, or you have another Atlassian application (or any Java web application) available at the same hostname and context path as Stash, then you should set a unique context path for Stash. See Moving Stash to a different context path.