Introduction
Due to the fact that not many, as it turned out, they know about Stash a little about him. On the manufacturer’s website the following description is given:
The Stash interface makes it easy to perform administrative and management tasks. Stash keeps your growing Git repositories safe within firewall range. Add users and user groups, set detailed rules directly from the UI (user interface). Create and manage repositories within Stash. To be aware of all the team cases and bring them to a single list is a matter of a couple of minutes.
Roughly say Stash from Atlassian - this is your local Githab. The special beauty of this tool is that it is very closely integrated with the same JIRA from Atlassian, which provides a much more convenient revision of the code for the task being performed and a single interface for this.
')
Installation
Installation of the specified product is quite simple. But I still found a rake for myself.
This was partly due to the fact that I put on CentOS. Until recently, I had almost no experience with this distribution.
In fact, this article is a free translation of the
Getting Started manual from the Atlassian website in the installation section of Linux.
It is useful for beginners.
Note:
All commands below are entered in the command line as root.
This installation option is recommended for test operation ! To start the server in commercial operation, you must perform a number of additional measures. This is all described in the installation article .
Later I will try to supplement the article with the order of transferring the server to the combat mode.First, we need to check the availability of the required versions of additional software.
Here we can see the supported versions.
1. Java
First we are invited to check the Java version installed on your server.
java -version
The rake number 1: JAVA versionI installed OpenJDK version 1.7.0 (java-1.7.0-openjdk.x86_64), everything was fine, except that for how long I did not wait for access to the web page was missing. Just a white blank page was displayed. As it turned out, it was best to put Java from Oracle - thanks to
vsb for the recommendation, I found the same recommendations somewhere on the forums when I solved this problem. Slightly more deployed under the spoiler.
Solution Rake â„–1I had to demolish OpenJDK and install OracleJDK. Download it
from here .
Through magical Google dug up a curious remark:
Stash Fails to Startup after installation when Running on OpenJDK
Symptoms
The following exception is reported when starting up Stash:
A fatal error has occurred
Atlassian Stash from starting correctly:
OpenJDK 64-Bit Server VM is an unsupported JVM.
Cause
OpenJDK is not a supported environment for Stash.
Resolution
Switch to the latest version of Oracle JDK to help resolve the problem.
True, I have everything started with OpenJDK and did not curse at all, but it still did not work. Strange in general.
2. Git
Also check the version of the installed package:
git --version
Here I was waiting for
Rake number 2 .
In CentOs 6.5, git 1.7.1 is in the base repository, and the minimum requirement is 1.7.6+
Everything would be great, but here all factors of my small experience with CentOS and yum came together at once. Prior to that, my entire administration experience was focused on Debian distributions. If this is not a problem for you, you can not look under the spoiler.
solution Rake â„–2You need to add an additional
rpmforge repository, there is
such a thing about how to add it. In short, then:
rpm --import apt.sw.be/RPM-GPG-KEY.dag.txt
rpm -K rpmforge-release-0.5.3-1.el6.rf. *. rpm
rpm -i rpmforge-release-0.5.3-1.el6.rf. *. rpm
Wherever I found recommendations for adding it, it is indicated that you need to translate rpmforge into enable.
Made.
yum update
and nothing has been updated.
yum install git
git has remained the old version.
The solution turned out to be simple, but I was looking for it, for some reason, for a long time.
just activate the repository
[rpmforge-extras] in the /etc/yum.repos.d/rpmforge.repo file
We set enable = 1, and here is the luck:
# git --version
git version 1.7.12.4
3.Perl
With this, CentOS 6.5 turned out to be all right.
# perl --version
This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi
minimum requirements:> = 5.8.8
4.Stash
Now we put Stash himself.
Download the archive distribution from
this page. And we deploy the archive to the desired installation location. For example, in
/ usr / local / stash This will be our
\ <Stash installation directory \>Before starting, we need to fix the file
\ <Stash installation directory \> /bin/setenv.shUncomment the parameter STASH_HOME and specify the location for stash data
eg
STASH_HOME = "/ home / stash-home-data"
!!! IMPORTANT!!!
Developers advise not to put data in the \ <Stash installation directory \> folder
This is due to the fact that when you need to update STASH, the data in the \ <Stash installation directory \> folder will be overwritten.
Everything, installation is complete. Now just run stash.
go to the folder where the stash is installed (this is our
\ <Stash installation directory \> )
bin / start-stash.sh
If everything started correctly, we will see
# bin / start-stash.sh
To run Stash in the foreground, start the server with start-stash.sh -fg
Starting Atlassian Stash as current user
Detecting JVM PermGen support ...
PermGen switch is supported. Setting to 256m \ n
Using STASH_HOME: / home / stash-home-data
Using CATALINA_BASE: /usr/local/etc/stash/atlassian-stash-2.10.1
Using CATALINA_HOME: /usr/local/etc/stash/atlassian-stash-2.10.1
Using CATALINA_TMPDIR: /usr/local/etc/stash/atlassian-stash-2.10.1/temp
Using JRE_HOME: / usr
Using CLASSPATH: /usr/local/etc/stash/atlassian-stash-2.10.1/bin/bootstrap.jar:/usr/local/etc/stash/atlassian-stash-2.10.1/bin/tomcat-juli.jar
Using CATALINA_PID: /usr/local/etc/stash/atlassian-stash-2.10.1/work/catalina.pid
Success! You can now use Stash at the following address:
localhost : 7990 /
If you cannot access Atlassian Stash, please read the troubleshooting guide at:
confluence.atlassian.com/display/STASHKB/Troubleshooting+Installation
As indicated, access to the web interface does not appear immediately, but within a few minutes. This is due to the preparation of data.
Next we open http: // <ip (dns) of your server>: 7990 / and follow through the installation wizard. I will not describe this process, since everything is elementary there.
PS: Discussion of the article and comments are waiting in the comments.
UPD: made some adjustments to the article, added a description.