Apache

Ansible Tasks: Create symbolic links for NGINX / Apache sites-enabled directory

nigel — Sun, 01 Jul 2018 10:25:47 +0000

Ansible Tasks: Create symbolic links for NGINX / Apache sites-enabled directory nigel Sun, 01/07/2018 - 11:25

Introduction

My first blog on Ansible, and it's here because it took me so long to figure it out. Ansible documentation is excellent - but of course like everything in life, if you aren't aware of all the concepts, it's difficult to know where to look first.

My requirement was to create symbolic links to the /etc/nginx/sites-enabled directory by looping through all the conf files in /etc/nginx/sites-available. This is equally valid for Apache servers which support the same mechanism for defining virtual hosts. I am currently building a VM for Drupal development and I am using Ansible for the configuration.

So my solution uses the find module to capture a list of conf files in /etc/nginx/sites-available and those are then saved in register for future usage. The file module is then invoked which will use the registered conf files. Note the placeholder on the destination directory - I need to access the item path but then filter it through basename to get the value I need. The force option is required because the nginx role I use already to build out the nginx configuration creates a default link which already exists and could choke my attempt to create a link for everything in /etc/nginx/sites-available.

Code Snippet

  tasks: 
 
    # Set symlinks to nginx sites-available directory
    - name: Get a list of all vhosts
      find:
        paths: /etc/nginx/sites-available
        patterns: "*.conf"
        file_type: file
      register: find

    - name: Apply symlinks in sites-enabled
      file:
        dest: /etc/nginx/sites-enabled/{{ item.path | basename }}
        src: "{{ item.path }}"
        state: link
        force: yes
      with_items: "{{ find.files }}"

blog terms

Ansible devops nginx Apache

Configure XDebug with PuPHPet, Vagrant, Apache, Ubuntu, PHP-FPM and PhpStorm

nigel — Sat, 20 Jun 2015 09:23:28 +0000

Configure XDebug with PuPHPet, Vagrant, Apache, Ubuntu, PHP-FPM and PhpStorm nigel Sat, 20/06/2015 - 10:23

PuPHPet is a terrific GUI to set up virtual machines for Web development and will build your orchestration script with Vagrant and Puppet. It now comes with a facility to include XDebug in your Vagrantfile meaning there is no longer an excuse for print_r() and error_log() debug traces in your code.

However, actually getting XDebug configured correctly with the IDE PhpStorm and Chrome browser is fiendishly fiddly, and there are many contradictory articles on the net on how to achieve it. Here is my take on how you shoud set up XDebug, in my case for Drupal development, although of course it'll work on any PHP framework or CMS. My development host is OS X on an ancient 17" Macbook Pro using the free Virtual Box product.

Firstly you should get your virtual machine working. I went for Ubuntu Trusty 64bit, Apache, with PHP 5.4 and most importantly don't forget to check the box for installing XDebug!!!

There are other resources on the Internet for installing VirtualBox, PhpStorm and Vagrant and getting your PuPHPet script up and running, so I won't cover that territory here.

There are three areas you need to configure to get XDebug working: Your Ubuntu virtual machine, your host's copy of PhpStorm, and your Chrome (or in my case Chromium) browser.

VM Configuration

Let's have a look at your virtual machine first. You will need to vagrant ssh into it and then sudo su so you have supervisor rights You need to determine where your xdebug.ini file is. To do that I built the mlocate database with the updatedb command then looked for the xdebug.ini. If you look at the output below, the file we want is /etc/php5/fpm/conf.d/20-xdebug.ini

[03:10 PM]-[root@local]-[/etc/php5/fpm/conf.d] 
# updatedb
 
[03:10 PM]-[root@local]-[/etc/php5/fpm/conf.d] 
# locate xdebug.ini
/etc/php5/cli/conf.d/20-xdebug.ini
/etc/php5/fpm/conf.d/20-xdebug.ini
/etc/php5/mods-available/xdebug.ini

Edit the /etc/php5/fpm/conf.d/20-xdebug.ini file. Yours will look something like this but you will need to change some values so don't just jump in and blithely copy/paste!

zend_extension="/usr/lib/php5/20121212/xdebug.so"
xdebug.idekey="PHPSTORM"  
xdebug.remote_host=10.0.2.15
xdebug.remote_port=100000
xdebug.remote_enable=1  
xdebug.remote_autostart=0  
xdebug.remote_handler="dbgp"

The first line is the location of the xdebug library. Use locate again to get the precise path on your VM

[03:18 PM]-[root@local]-[/etc/php5/fpm/conf.d] 
# locate xdebug.so
/usr/lib/php5/20121212/xdebug.so

The second line is the cookie ID which should be PHPSTORM to coincide with the Chrome extension's built-in configuration we will deal with later. The third line is the IP Address of the local Ethernet adapter. Discover this with ifconfig

[03:21 PM]-[root@local]-[/etc/php5/fpm/conf.d] 
# ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:34:6f:30  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe34:6f30/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:60997 errors:0 dropped:0 overruns:0 frame:0
          TX packets:49863 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8756579 (8.7 MB)  TX bytes:4807502 (4.8 MB)
 
eth1      Link encap:Ethernet  HWaddr 08:00:27:40:9c:6a  
          inet addr:192.168.56.101  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe40:9c6a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:127578 errors:0 dropped:0 overruns:0 frame:0
          TX packets:131555 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:21689518 (21.6 MB)  TX bytes:153361934 (153.3 MB)
 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:100167 errors:0 dropped:0 overruns:0 frame:0
          TX packets:100167 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:171493822 (171.4 MB)  TX bytes:171493822 (171.4 MB)

The fourth configuration is the port for XDebug. You should use 10000 (or rather not 9000) to avoid a clash with PHP-FPM The rest of the configuration is default and can be left as is. Once your xdebug.ini file is saved you need to restart Apache and FPM

[03:27 PM]-[root@local]-[/var/www/whatsapp-viewer]-[git feature/bulk-operations] 
# service apache2 restart
 * Restarting web server apache2                                                                         [ OK ] 
 
[03:27 PM]-[root@local]-[/var/www/whatsapp-viewer]-[git feature/bulk-operations] 
# service php5-fpm restart
php5-fpm stop/waiting
php5-fpm start/running, process 24257

PhpStorm Configuration

Go to File->Default Settings->Language & Frameworks->PHP and makde sure your Interpreter is set correctly to your VM's PHP interpreter.

Open up the Debug tab and ensure your settings look like those displayed here - note the port of 10000 matches the value we already put into the xdebug.ini file

Go to Run->Edit Configurations->Defaults->PHP Remote Debug and ensure that the server is your development domain and the ide key is PHPSTORM as we mentioned before.

Chrome Browser Configuration

Next you need to be able to switch debugging on and off on your Chrome browser. There are different ways of achieving this but by far the best is by installing the XDebug extension to the browser.

Once the extension has been added made sure the configuration represents PhpStorm

Runtime

Ok it is now time to check out our configuration. You'll need to enable debugging in your browser, set the listener to on in PhpStorm, and set some breakpoints. Let's show you!

This small image shows the PhpStorm controls in the top right corner. Make sure the fourth icon from the left (represented by a small telephone symbol) is listening for PHP debug connections

Go to your code and click in the margin to set a breakpoint which will stop the execution so you can inspect variables

In Chrome make sure you can see the XDebug icon in the far right of the URL bar and it is green and enabled

Navigate around your application in the Chrome browser and once you hit the breakpoint the execution will pause and you will be able to inspect your variables! Success!

blog terms

Drupal Development Linux Apache PHP

openSUSE 12.3 Installation of GitLab, Nginx, Apache and Drupal PHP

nigel — Thu, 26 Sep 2013 11:17:36 +0000

openSUSE 12.3 Installation of GitLab, Nginx, Apache and Drupal PHP nigel Thu, 26/09/2013 - 12:17

This tutorial blog is intended for those who wish to run concurrent instances of Nginx and Apache web servers on Linux openSUSE 12.3, the Nginx server being used for the Ruby on Rails GitLab application, whilst Apache will co-exist for serving pages from my PHP-based Drupal sites. Of course, the exercise is valid for Wordpress and Joomla and other PHP-based CMS frameworks.

The recommended approach for running both Nginx and Apache is to have one server in front of the other. In this case the front server will be Nginx and will pass requests for the PHP sites on to Apache to deal with. Obviously since both sites would normally be listening for incoming requests on port 80, we'll have to assign the back server Apache another port number. More on this as we progress through the tutorial.

Nginx / GitLab

The starting point for the Nginx / Gitlab build is jniltinho's script at https://gist.github.com/jniltinho/5565606. The script is a little out of date, and I prefer to 'hand crank' rather than run scripts so I can see what's going on. Log in as root and clean and refresh the repositories

linux-vuby:~ # zypper clean && zypper refresh
All repositories have been cleaned up.
Repository 'openSUSE-12.3-1.7' is up to date.
Repository 'openSUSE-12.3-Non-Oss' is up to date.
Repository 'openSUSE-12.3-Update' is up to date.
Repository 'openSUSE-12.3-Update-Non-Oss' is up to date.
All repositories have been refreshed.
linux-vuby:~ #

Add the requirements. Although my openSUSE 12.3 was a relatively clean build with almost nothing on it, one or two requirements had been installed previously.

linux-vuby:/ # zypper install -y sudo vim vim-data ctags postfix python
Loading repository data...
Reading installed packages...
'vim' is already installed.
No update candidate for 'vim-7.3.831-1.1.1.x86_64'. The highest available version is already installed.
'postfix' is already installed.
No update candidate for 'postfix-2.9.6-1.2.1.x86_64'. The highest available version is already installed.
'sudo' is already installed.
No update candidate for 'sudo-1.8.6p3-3.13.1.x86_64'. The highest available version is already installed.
'ctags' is already installed.
No update candidate for 'ctags-2011.8.2-9.1.1.x86_64'. The highest available version is already installed.
'vim-data' is already installed.
No update candidate for 'vim-data-7.3.831-1.1.1.noarch'. The highest available version is already installed.
Resolving package dependencies...
 
The following NEW package is going to be installed:
  python 
 
1 new package to install.
Overall download size: 274.4 KiB. After the operation, additional 1.3 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package python-2.7.3-10.8.1.x86_64                        (1/1), 274.4 KiB (  1.3 MiB unpacked)
Retrieving: python-2.7.3-10.8.1.x86_64.rpm .............................................[done (1.7 MiB/s)]
(1/1) Installing: python-2.7.3-10.8.1 ..............................................................[done]
linux-vuby:/ #

Install Nginx

linux-vuby:~ #  zypper install -y nginx
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  GeoIP libGeoIP1 nginx 
 
The following recommended package was automatically selected:
  GeoIP 
 
3 new packages to install.
Overall download size: 1.2 MiB. After the operation, additional 3.7 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package libGeoIP1-1.4.8-5.2.1.x86_64                      (1/3),  73.4 KiB (229.4 KiB unpacked)
Retrieving: libGeoIP1-1.4.8-5.2.1.x86_64.rpm .......................................................[done]
Retrieving package GeoIP-1.4.8-5.2.1.x86_64                          (2/3), 491.7 KiB (  1.3 MiB unpacked)
Retrieving: GeoIP-1.4.8-5.2.1.x86_64.rpm .............................................[done (815.8 KiB/s)]
Retrieving package nginx-1.2.9-3.4.1.x86_64                          (3/3), 614.0 KiB (  2.2 MiB unpacked)
Retrieving: nginx-1.2.9-3.4.1.x86_64.rpm .............................................[done (554.8 KiB/s)]
(1/3) Installing: libGeoIP1-1.4.8-5.2.1 ............................................................[done]
(2/3) Installing: GeoIP-1.4.8-5.2.1 ................................................................[done]
(3/3) Installing: nginx-1.2.9-3.4.1 ................................................................[done]
linux-vuby:~ #

Install mysql database server

linux-vuby:/ # zypper install -y mysql-community-server 
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  mysql-community-server mysql-community-server-client mysql-community-server-errormessages 
 
3 new packages to install.
Overall download size: 4.9 MiB. After the operation, additional 56.8 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package mysql-community-server-errormessages-5.5.32-1.8.1.x86_64
                                                                     (1/3), 187.3 KiB (  1.5 MiB unpacked)
Retrieving: mysql-community-server-errormessages-5.5.32-1.8.1.x86_64.rpm ...........................[done]
Retrieving package mysql-community-server-client-5.5.32-1.8.1.x86_64 (2/3), 761.9 KiB ( 17.1 MiB unpacked)
Retrieving: mysql-community-server-client-5.5.32-1.8.1.x86_64.rpm ......................[done (1.9 MiB/s)]
Retrieving package mysql-community-server-5.5.32-1.8.1.x86_64        (3/3),   4.0 MiB ( 38.1 MiB unpacked)
Retrieving: mysql-community-server-5.5.32-1.8.1.x86_64.rpm .............................[done (1.7 MiB/s)]
(1/3) Installing: mysql-community-server-errormessages-5.5.32-1.8.1 ................................[done]
(2/3) Installing: mysql-community-server-client-5.5.32-1.8.1 .......................................[done]
(3/3) Installing: mysql-community-server-5.5.32-1.8.1 ..............................................[done]
linux-vuby:/ #

Time server and python pygments

linux-vuby:/ # zypper install -y ntp python-Pygments
Loading repository data...
Reading installed packages...
'ntp' is already installed.
No update candidate for 'ntp-4.2.6p5-9.3.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  python-Pygments python-distribute 
 
2 new packages to install.
Overall download size: 889.4 KiB. After the operation, additional 4.7 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package python-distribute-0.6.31-2.1.1.noarch             (1/2), 285.6 KiB (  1.1 MiB unpacked)
Retrieving: python-distribute-0.6.31-2.1.1.noarch.rpm ................................[done (741.0 KiB/s)]
Retrieving package python-Pygments-1.5-5.1.1.noarch                  (2/2), 603.8 KiB (  3.6 MiB unpacked)
Retrieving: python-Pygments-1.5-5.1.1.noarch.rpm ...................................................[done]
(1/2) Installing: python-distribute-0.6.31-2.1.1 ...................................................[done]
(2/2) Installing: python-Pygments-1.5-5.1.1 ........................................................[done]
linux-vuby:/ #

Ruby, redis, curl, git-core, wget and findutils

linux-vuby:/ # zypper install -y ruby redis curl git-core wget  findutils-locate
Loading repository data...
Reading installed packages...
'curl' is already installed.
No update candidate for 'curl-7.28.1-4.17.1.x86_64'. The highest available version is already installed.
'wget' is already installed.
No update candidate for 'wget-1.13.4-15.1.1.x86_64'. The highest available version is already installed.
'findutils-locate' is already installed.
No update candidate for 'findutils-locate-4.5.10-10.8.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  git-core redis ruby ruby19 
 
4 new packages to install.
Overall download size: 6.8 MiB. After the operation, additional 33.2 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package git-core-1.8.1.4-1.1.1.x86_64                     (1/4),   2.8 MiB ( 16.2 MiB unpacked)
Retrieving: git-core-1.8.1.4-1.1.1.x86_64.rpm ..........................................[done (1.9 MiB/s)]
Retrieving package redis-2.4.15-3.1.1.x86_64                         (2/4), 256.4 KiB (930.1 KiB unpacked)
Retrieving: redis-2.4.15-3.1.1.x86_64.rpm ..........................................................[done]
Retrieving package ruby19-1.9.3.p392-1.9.1.x86_64                    (3/4),   3.7 MiB ( 16.1 MiB unpacked)
Retrieving: ruby19-1.9.3.p392-1.9.1.x86_64.rpm .........................................[done (2.1 MiB/s)]
Retrieving package ruby-1.9.3-15.6.1.x86_64                          (4/4),  14.2 KiB (  1.9 KiB unpacked)
Retrieving: ruby-1.9.3-15.6.1.x86_64.rpm ...........................................................[done]
(1/4) Installing: git-core-1.8.1.4-1.1.1 ...........................................................[done]
(2/4) Installing: redis-2.4.15-3.1.1 ...............................................................[done]
Additional rpm output:
redirecting to systemctl  try-restart redis
To start the database server, create your configuration
starting from /etc/redis/default.conf.example, place it
in /etc/redis and do: 
 sudo rcredis start; sudo insserv redis
 
 
(3/4) Installing: ruby19-1.9.3.p392-1.9.1 ..........................................................[done]
(4/4) Installing: ruby-1.9.3-15.6.1 ................................................................[done]
Additional rpm output:
update-alternatives: using /usr/bin/erb1.9 to provide /usr/bin/erb (erb) in auto mode
update-alternatives: using /usr/bin/gem1.9 to provide /usr/bin/gem (gem) in auto mode
update-alternatives: using /usr/bin/irb1.9 to provide /usr/bin/irb (irb) in auto mode
update-alternatives: using /usr/bin/rake1.9 to provide /usr/bin/rake (rake) in auto mode
update-alternatives: using /usr/bin/rdoc1.9 to provide /usr/bin/rdoc (rdoc) in auto mode
update-alternatives: using /usr/bin/ri1.9 to provide /usr/bin/ri (ri) in auto mode
update-alternatives: using /usr/bin/ruby1.9 to provide /usr/bin/ruby (ruby) in auto mode
update-alternatives: using /usr/bin/testrb1.9 to provide /usr/bin/testrb (testrb) in auto mode
 
 
linux-vuby:/ #

Ruby and importantly the ruby gem bundler

linux-vuby:/ # zypper install -y rubygem-bundler rubygem-mysql2 libxml2-devel libxslt-devel
Loading repository data...
Reading installed packages...
'libxml2-devel' is already installed.
No update candidate for 'libxml2-devel-2.9.0-2.17.1.x86_64'. The highest available version is already installed.
'libxslt-devel' is already installed.
No update candidate for 'libxslt-devel-1.1.28-3.4.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  rubygem-bundler rubygem-mysql2 
 
2 new packages to install.
Overall download size: 460.3 KiB. After the operation, additional 994.9 KiB will be used.
Continue? [y/n/?] (y): y
Retrieving package rubygem-bundler-1.2.3-2.1.1.x86_64                (1/2), 371.1 KiB (781.4 KiB unpacked)
Retrieving: rubygem-bundler-1.2.3-2.1.1.x86_64.rpm .................................................[done]
Retrieving package rubygem-mysql2-0.3.11-4.1.1.x86_64                (2/2),  89.1 KiB (213.5 KiB unpacked)
Retrieving: rubygem-mysql2-0.3.11-4.1.1.x86_64.rpm .................................................[done]
(1/2) Installing: rubygem-bundler-1.2.3-2.1.1 ......................................................[done]
(2/2) Installing: rubygem-mysql2-0.3.11-4.1.1 ......................................................[done]
linux-vuby:/ #

Ruby development, make and the C++ compiler

linux-vuby:/ # zypper install -y ruby-devel make gcc libicu-devel libmysqlclient-devel gcc-c++
Loading repository data...
Reading installed packages...
'gcc' is already installed.
No update candidate for 'gcc-4.7-7.1.1.x86_64'. The highest available version is already installed.
'gcc-c++' is already installed.
No update candidate for 'gcc-c++-4.7-7.1.1.x86_64'. The highest available version is already installed.
'make' is already installed.
No update candidate for 'make-3.82-154.1.1.x86_64'. The highest available version is already installed.
'libicu-devel' is already installed.
No update candidate for 'libicu-devel-49.1-6.1.1.x86_64'. The highest available version is already installed.
'libmysqlclient-devel' is already installed.
No update candidate for 'libmysqlclient-devel-5.5.32-1.8.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  ruby-common ruby-devel ruby19-devel 
 
3 new packages to install.
Overall download size: 2.6 MiB. After the operation, additional 15.7 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package ruby-common-2.0-3.1.1.noarch                      (1/3),  11.0 KiB ( 13.7 KiB unpacked)
Retrieving: ruby-common-2.0-3.1.1.noarch.rpm .......................................................[done]
Retrieving package ruby19-devel-1.9.3.p392-1.9.1.x86_64              (2/3),   2.6 MiB ( 15.7 MiB unpacked)
Retrieving: ruby19-devel-1.9.3.p392-1.9.1.x86_64.rpm ...................................[done (1.8 MiB/s)]
Retrieving package ruby-devel-1.9.3-15.6.1.x86_64                      (3/3),   9.8 KiB (    0 B unpacked)
Retrieving: ruby-devel-1.9.3-15.6.1.x86_64.rpm .....................................................[done]
(1/3) Installing: ruby-common-2.0-3.1.1 ............................................................[done]
(2/3) Installing: ruby19-devel-1.9.3.p392-1.9.1 ....................................................[done]
(3/3) Installing: ruby-devel-1.9.3-15.6.1 ..........................................................[done]
linux-vuby:/ #

Installing charlock_holmes proved a complete nightmare and only by extensive googling over a protracted period of time did I find a solution. If you attempt to install it with gem install charlock_holmes you will get the following error message:

Building native extensions.  This could take a while...                                                  
ERROR:  Error installing charlock_holmes:                                                                
        ERROR: Failed to build gem native extension.                                                     
 
        /usr/bin/ruby1.9 extconf.rb                                                                      
checking for main() in -licui18n... yes                                                                  
checking for main() in -licui18n... yes                                                                  
checking for unicode/ucnv.h... yes                                                                       
  -- tar zxvf file-5.08.tar.gz                                                                           
  -- ./configure --prefix=/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/dst/ --disable-shared --enable-static --with-pic                                                               
  -- make -C src install                                                                                 
  -- make -C magic install                                                                               
*** extconf.rb failed ***                                                                                
Could not create Makefile due to some reason, probably lack of                                           
necessary libraries and/or headers.  Check the mkmf.log file for more                                    
details.  You may need configuration options.                                                            
 
Provided configuration options:                                                                          
        --with-opt-dir                                                                                   
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/usr/bin/ruby1.9
        --with-icu-dir
        --without-icu-dir
        --with-icu-include
        --without-icu-include=${icu-dir}/include
        --with-icu-lib
        --without-icu-lib=${icu-dir}/
        --with-icui18nlib
        --without-icui18nlib
        --with-icui18nlib
        --without-icui18nlib
/usr/lib64/ruby/1.9.1/fileutils.rb:1515:in `stat': No such file or directory - /usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/dst/lib/libmagic.a (Errno::ENOENT)
        from /usr/lib64/ruby/1.9.1/fileutils.rb:1515:in `block in fu_each_src_dest'
        from /usr/lib64/ruby/1.9.1/fileutils.rb:1531:in `fu_each_src_dest0'
        from /usr/lib64/ruby/1.9.1/fileutils.rb:1513:in `fu_each_src_dest'
        from /usr/lib64/ruby/1.9.1/fileutils.rb:395:in `cp'
        from extconf.rb:66:in `'
 
 
Gem files will remain installed in /usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9 for inspection.
Results logged to /usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/gem_make.out

The circumvention is documented here. The upshot is for some reason the script attempts to statically link libmagic.a rather than using the system libmagic.so. Fix this by unsetting the environmental variable CONFIG_SITE

linux-vuby:~ #  echo $CONFIG_SITE
/usr/share/site/x86_64-unknown-linux-gnu
linux-vuby:~ # unset CONFIG_SITE
linux-vuby:~ # echo $CONFIG_SITE
 
linux-vuby:~ # gem install -V charlock_holmes --version '0.6.9'
GET https://rubygems.org/specs.4.8.gz
connection reset after 1 requests, retrying
GET https://rubygems.org/specs.4.8.gz
302 Moved Temporarily
GET https://s3.amazonaws.com/production.s3.rubygems.org/specs.4.8.gz
200 OK
Installing gem charlock_holmes-0.6.9
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/.gitignore
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/.rspec
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/Gemfile
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/Gemfile.lock
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/MIT-LICENSE
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/README.md
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/Rakefile
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/benchmark/detection.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/benchmark/test.txt
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/charlock_holmes.gemspec
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/common.h
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/converter.c
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/encoding_detector.c
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/ext.c
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/extconf.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/src/file-5.08.tar.gz
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/lib/charlock_holmes.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/lib/charlock_holmes/encoding_detector.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/lib/charlock_holmes/string.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/lib/charlock_holmes/version.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/converter_spec.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/encoding_detector_spec.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/AnsiGraph.psm1
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/TwigExtensionsDate.es.yml
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/cl-messagepack.lisp
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/core.rkt
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/hello_world
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/laholator.py
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/fixtures/repl2.cljs
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/spec_helper.rb
/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/spec/string_method_spec.rb
Building native extensions.  This could take a while...
/usr/bin/ruby1.9 extconf.rb
checking for main() in -licui18n... yes
checking for main() in -licui18n... yes
checking for unicode/ucnv.h... yes
  -- tar zxvf file-5.08.tar.gz
  -- ./configure --prefix=/usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/ext/charlock_holmes/dst/ --disable-shared --enable-static --with-pic
  -- make -C src install
  -- make -C magic install
checking for main() in -lmagic_ext... yes
checking for magic.h... yes
creating Makefile
 
make
compiling ext.c
In file included from ext.c:1:0:
common.h:14:14: warning: ‘charlock_new_enc_str’ defined but not used [-Wunused-function]
common.h:23:14: warning: ‘charlock_new_str’ defined but not used [-Wunused-function]
common.h:32:14: warning: ‘charlock_new_str2’ defined but not used [-Wunused-function]
compiling encoding_detector.c
In file included from encoding_detector.c:3:0:
common.h:14:14: warning: ‘charlock_new_enc_str’ defined but not used [-Wunused-function]
compiling converter.c
In file included from converter.c:2:0:
common.h:23:14: warning: ‘charlock_new_str’ defined but not used [-Wunused-function]
common.h:32:14: warning: ‘charlock_new_str2’ defined but not used [-Wunused-function]
linking shared-object charlock_holmes/charlock_holmes.so
 
make install
/usr/bin/install -c -m 0755 charlock_holmes.so /usr/lib64/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9/lib/charlock_holmes
installing default charlock_holmes libraries
Successfully installed charlock_holmes-0.6.9
1 gem installed
Installing ri documentation for charlock_holmes-0.6.9...
rdoc --ri --op /usr/lib64/ruby/gems/1.9.1/doc/charlock_holmes-0.6.9/ri --charset=UTF-8 lib --title charlock_holmes-0.6.9 Documentation --quiet
Installing RDoc documentation for charlock_holmes-0.6.9...
rdoc --op /usr/lib64/ruby/gems/1.9.1/doc/charlock_holmes-0.6.9/rdoc --charset=UTF-8 lib --title charlock_holmes-0.6.9 Documentation --quiet

Add the git group and git user

linux-vuby:/ # groupadd git
linux-vuby:/ # useradd -m -G git --system -s /bin/sh -c 'GitLab' -d /home/git git
linux-vuby:/ #

linux-vuby:/ # su - git
linux-vuby:~> pwd
/home/git
linux-vuby:~>

git clone the gitlab shell

linux-vuby:~> git config --global http.sslVerify false
linux-vuby:~> git clone https://github.com/gitlabhq/gitlab-shell.git
Cloning into 'gitlab-shell'...
remote: Counting objects: 801, done.
remote: Compressing objects: 100% (481/481), done.
remote: Total 801 (delta 400), reused 673 (delta 291)
Receiving objects: 100% (801/801), 125.88 KiB, done.
Resolving deltas: 100% (400/400), done.
linux-vuby:~>

Checkout the version we need

linux-vuby:~> cd gitlab-shell/
linux-vuby:~/gitlab-shell> git checkout v1.7.1
Note: checking out 'v1.7.1'.
 
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
 
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
 
  git checkout -b new_branch_name
 
HEAD is now at 2c238b7... GitLab shell up to 1.7.1
linux-vuby:~/gitlab-shell>

Next the config file needs to be created by copying the sample

linux-vuby:~/gitlab-shell> cp config.yml.example config.yml
linux-vuby:~/gitlab-shell>

Change the gitlab url setting in the config file to what you are intending to use. Since this is a try-out on localhost for me, I'm going to call it localhost.gitlab.badzilla.co.uk

# Url to gitlab instance. Used for api calls. Should end with a slash.
gitlab_url: "http://localhost.gitlab.badzilla.co.uk/"

Run the installation script

linux-vuby:~/gitlab-shell> ./bin/install
mkdir -p /home/git/repositories: true
mkdir -p /home/git/.ssh: true
chmod 700 /home/git/.ssh: true
touch /home/git/.ssh/authorized_keys: true
chmod 600 /home/git/.ssh/authorized_keys: true
chmod -R ug+rwX,o-rwx /home/git/repositories: true
find /home/git/repositories -type d -print0 | xargs -0 chmod g+s: true
linux-vuby:~/gitlab-shell>

Create a host file entry for gitlab. /etc/hosts

127.0.0.1       localhost
127.0.0.1       localhost.gitlab.badzilla.co.uk

Logout of the git user back to root and create a password for the mysql root

linux-vuby:~/gitlab-shell> logout
linux-vuby:/ # rcmysql start
redirecting to systemctl  start mysql
linux-vuby:/ # mysqladmin -u root password your_password_here
linux-vuby:/ # rcmysql restart
redirecting to systemctl  restart mysql
linux-vuby:/ #

Create the gitlab mysql user and the database

linux-vuby:/ # echo 'CREATE USER gitlab@localhost IDENTIFIED BY "gitlab";
> CREATE DATABASE IF NOT EXISTS `gitlabhq_production` DEFAULT CHARACTER SET `utf8` COLLATE `utf8_unicode_ci`;
> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER ON `gitlabhq_production`.* TO gitlab@localhost;' > /tmp/create_bd_git.sql
linux-vuby:/ # mysql -u root -pyour_password_here < /tmp/create_bd_git.sql 
linux-vuby:/ # rm -f /tmp/create_bd_git.sql

The redis configuration file needs to be created and the service started

linux-vuby:/ # sudo -u redis -H cp /etc/redis/default.conf.example /etc/redis/default.conf
linux-vuby:/ # rcredis restart
redirecting to systemctl  restart redis
linux-vuby:/ #

Now it's time to clone the website. Switch to the git user and clone in the git repository

linux-vuby:/ # su - git
linux-vuby:~> git clone https://github.com/gitlabhq/gitlabhq.git gitlab
Cloning into 'gitlab'...
remote: Finding bitmap roots...
remote: Reusing existing pack: 57197, done.
remote: Counting objects: 429, done.
remote: Compressing objects: 100% (264/264), done.
remote: Total 57626 (delta 208), reused 331 (delta 155)
Receiving objects: 100% (57626/57626), 25.51 MiB | 1.08 MiB/s, done.
Resolving deltas: 100% (39493/39493), done.
linux-vuby:~>

May as well use the latest and greatest stable release - 6-1 at the time of writing this blog.

linux-vuby:~> cd gitlab
linux-vuby:~/gitlab> git checkout 6-1-stable
Branch 6-1-stable set up to track remote branch 6-1-stable from origin.
Switched to a new branch '6-1-stable'
linux-vuby:~/gitlab>

Copy the default configuration file

linux-vuby:~/gitlab> cp config/gitlab.yml.example config/gitlab.yml
linux-vuby:~/gitlab>

Edit the config file to reflect your domain, so change the host: setting as a minimum, but you may also want to change the email addresses. /home/git/gitlab/config/gitlab.yml

host: localhost.gitlab.badzilla.co.uk
email_from: gitlab@localhost
support_email: support@localhost

Change the ownership of everything under the git user's home directory to ensure the group git has access. Add a sockets directory and ensure the nginx user is part of the git group to prevent permission issues.

linux-vuby:/ # sudo -u git -H mkdir /home/git/gitlab/tmp/sockets
linux-vuby:/ # usermod -g git nginx
linux-vuby:/ # chown -R git:git /home/git
linux-vuby:/ # chmod -R g+w /home/git/gitlab

The manual suggests checking that the git user has the necessary permissions, but this can be safely skipped because the permissions are ok. Still, here for completeness.

linux-vuby:~/gitlab> chown -R git log/
linux-vuby:~/gitlab> chown -R git tmp/
linux-vuby:~/gitlab> chmod -R u+rwX log/
linux-vuby:~/gitlab> chmod -R u+rwX tmp/
linux-vuby:~/gitlab>

Create the satellites directory

linux-vuby:~/gitlab> mkdir /home/git/gitlab-satellites
linux-vuby:~/gitlab>

Create a temporary directory for the process ids

linux-vuby:~/gitlab> mkdir tmp/pids/
linux-vuby:~/gitlab> chmod -R u+rwX tmp/pids/
linux-vuby:~/gitlab>

Copy the example unicorn and mysql config files

linux-vuby:~/gitlab> cp /home/git/gitlab/config/unicorn.rb.example /home/git/gitlab/config/unicorn.rb
linux-vuby:~/gitlab> cp /home/git/gitlab/config/database.yml.mysql /home/git/gitlab/config/database.yml
linux-vuby:~/gitlab>

Edit the database configuration file to reflect the gitlab user and its password /home/git/gitlab/config/database.yml

  username: gitlab
  password: gitlab

Now install the deployment. I ran into problems here because the deployment attempts another install of charlock_holmes - so I had to unset CONFIG_SITE again.

linux-vuby:~/gitlab> unset CONFIG_SITE
linux-vuby:~/gitlab> bundle install --deployment --without development test postgres
Fetching gem metadata from https://rubygems.org/.......
Fetching gem metadata from https://rubygems.org/..
Using rake (10.1.0) 
Using i18n (0.6.1) 
Using multi_json (1.7.9) 
Using activesupport (3.2.13) 
Using builder (3.0.4) 
Using activemodel (3.2.13) 
Using erubis (2.7.0) 
Using journey (1.0.4) 
Using rack (1.4.5) 
Using rack-cache (1.2) 
Using rack-test (0.6.2) 
Using hike (1.2.3) 
Using tilt (1.4.1) 
Using sprockets (2.2.2) 
Using actionpack (3.2.13) 
Using mime-types (1.25) 
Using polyglot (0.3.3) 
Using treetop (1.4.14) 
Using mail (2.5.4) 
Using actionmailer (3.2.13) 
Using arel (3.0.2) 
Using tzinfo (0.3.37) 
Using activerecord (3.2.13) 
Using activeresource (3.2.13) 
Using bundler (1.2.3) 
Using rack-ssl (1.3.3) 
Using json (1.7.7) 
Using rdoc (3.12.2) 
Using thor (0.18.1) 
Using railties (3.2.13) 
Using rails (3.2.13) 
Using acts-as-taggable-on (2.4.1) 
Using asciidoctor (0.1.3) 
Using backports (3.3.2) 
Using bcrypt-ruby (3.1.1) 
Using sass (3.2.9) 
Using bootstrap-sass (2.3.2.0) 
Using carrierwave (0.8.0) 
Using timers (1.1.0) 
Using celluloid (0.14.1) 
Installing charlock_holmes (0.6.9.4) with native extensions 
Installing coffee-script-source (1.6.2) 
Installing execjs (1.4.0) 
Installing coffee-script (2.2.0) 
Installing coffee-rails (3.2.2) 
Installing chunky_png (1.2.8) 
Installing fssm (0.2.10) 
Installing compass (0.12.2) 
Installing compass-rails (1.0.3) 
Installing sass-rails (3.2.6) 
Installing chosen-rails (1.0.0) 
Installing colored (1.2) 
Installing connection_pool (1.1.0) 
Installing d3_rails (3.1.10) 
Installing descendants_tracker (0.0.1) 
Installing orm_adapter (0.4.0) 
Installing warden (1.2.3) 
Installing devise (2.2.5) 
Installing diff-lcs (1.2.4) 
Installing dotenv (0.8.0) 
Installing enumerize (0.6.1) 
Installing escape_utils (0.2.4) with native extensions 
Installing eventmachine (1.0.3) with native extensions 
Installing excon (0.13.4) 
Installing multipart-post (1.2.0) 
Installing faraday (0.8.7) 
Installing faraday_middleware (0.9.0) 
Installing formatador (0.2.4) 
Installing net-ssh (2.6.8) 
Installing net-scp (1.0.4) 
Installing nokogiri (1.5.10) with native extensions 
Installing ruby-hmac (0.4.0) 
Installing fog (1.3.1) 
Installing font-awesome-rails (3.2.1.2) 
Installing foreman (0.63.0) 
Installing gemoji (1.2.1) 
Installing posix-spawn (0.3.6) with native extensions 
Installing yajl-ruby (1.1.0) with native extensions 
Installing pygments.rb (0.4.2) 
Installing github-linguist (2.3.4) 
Installing github-markdown (0.5.3) with native extensions 
Installing github-markup (0.7.5) 
Installing gitlab-grit (2.6.0) 
Installing sanitize (2.0.3) 
Installing stringex (1.5.1) 
Installing gitlab-gollum-lib (1.0.1) 
Installing gitlab-grack (1.0.1) 
Installing gitlab-pygments.rb (0.3.2) 
Installing gitlab_git (2.3.1) 
Installing gitlab_meta (6.0) 
Installing net-ldap (0.3.1) 
Installing hashie (1.2.0) 
Installing omniauth (1.1.4) 
Installing pyu-ruby-sasl (0.0.3.3) 
Installing rubyntlm (0.1.1) 
Installing gitlab_omniauth-ldap (1.0.3) 
Installing gon (4.1.1) 
Installing multi_xml (0.5.4) 
Installing rack-accept (0.4.5) 
Installing rack-mount (0.8.3) 
Installing virtus (0.5.5) 
Installing grape (0.4.1) 
Installing grape-entity (0.3.0) 
Installing haml (4.0.3) 
Installing haml-rails (0.4) 
Installing httparty (0.11.0) 
Installing hipchat (0.9.0) 
Installing http_parser.rb (0.5.3) with native extensions 
Installing httpauth (0.2.0) 
Installing jquery-atwho-rails (0.3.0) 
Installing jquery-rails (2.1.3) 
Installing turbolinks (1.2.0) 
Installing jquery-turbolinks (1.0.0) 
Installing jquery-ui-rails (2.0.2) 
Installing jwt (0.1.8) 
Installing kaminari (0.14.1) 
Installing kgio (2.8.0) with native extensions 
Installing libv8 (3.11.8.17) 
Installing modernizr (2.6.2) 
Installing mysql2 (0.3.11) with native extensions 
Installing oauth (0.4.7) 
Installing oauth2 (0.8.1) 
Installing omniauth-oauth2 (1.1.1) 
Installing omniauth-github (1.1.0) 
Installing omniauth-google-oauth2 (0.1.19) 
Installing omniauth-oauth (1.0.1) 
Installing omniauth-twitter (0.0.17) 
Installing rack-protection (1.5.0) 
Installing raindrops (0.11.0) with native extensions 
Installing raphael-rails (2.1.2) 
Installing redcarpet (2.2.2) with native extensions 
Installing redis (3.0.4) 
Installing redis-store (1.1.4) 
Installing redis-rack (1.4.4) 
Installing redis-actionpack (3.2.4) 
Installing redis-activesupport (3.2.4) 
Installing redis-namespace (1.3.1) 
Installing redis-rails (3.2.4) 
Installing ref (1.0.5) 
Installing seed-fu (2.2.0) 
Installing select2-rails (3.4.2) 
Installing settingslogic (2.0.9) 
Installing sidekiq (2.14.0) 
Installing simple_oauth (0.1.9) 
Installing sinatra (1.4.3) 
Installing six (0.2.0) 
Installing temple (0.6.5) 
Installing slim (2.0.0) 
Installing stamp (0.5.0) 
Installing state_machine (1.2.0) 
Installing therubyracer (0.11.4) with native extensions 
Installing twitter-stream (0.1.16) 
Installing tinder (1.9.2) 
Installing uglifier (2.1.1) 
Installing underscore-rails (1.4.4) 
Installing unicorn (4.6.3) with native extensions 
Your bundle is complete! It was installed into ./vendor/bundle
Post-install message from haml:
 
HEADS UP! Haml 4.0 has many improvements, but also has changes that may break
your application:
 
* Support for Ruby 1.8.6 dropped
* Support for Rails 2 dropped
* Sass filter now always outputs <style> tags
* Data attributes are now hyphenated, not underscored
* html2haml utility moved to the html2haml gem
* Textile and Maruku filters moved to the haml-contrib gem
 
For more info see:
 
http://rubydoc.info/github/haml/haml/file/CHANGELOG.md
 
Post-install message from httparty:
When you HTTParty, you must party hard!
linux-vuby:~/gitlab>

Time to build the database

linux-vuby:~/gitlab> bundle exec rake gitlab:setup RAILS_ENV=production
This will create the necessary database tables and seed the database.
You will lose any previous data stored in the database.
Do you want to continue (yes/no)? yes
 
gitlabhq_production already exists
-- create_table("deploy_keys_projects", {:force=>true})
   -> 0.2450s
-- add_index("deploy_keys_projects", ["project_id"], {:name=>"index_deploy_keys_projects_on_project_id"})
   -> 0.1787s
-- create_table("events", {:force=>true})
   -> 0.1675s
-- add_index("events", ["action"], {:name=>"index_events_on_action"})
   -> 0.1787s
-- add_index("events", ["author_id"], {:name=>"index_events_on_author_id"})
   -> 0.1786s
-- add_index("events", ["created_at"], {:name=>"index_events_on_created_at"})
   -> 0.1677s
-- add_index("events", ["project_id"], {:name=>"index_events_on_project_id"})
   -> 0.1787s
-- add_index("events", ["target_id"], {:name=>"index_events_on_target_id"})
   -> 0.1787s
-- add_index("events", ["target_type"], {:name=>"index_events_on_target_type"})
   -> 0.1787s
-- create_table("forked_project_links", {:force=>true})
   -> 0.1583s
-- add_index("forked_project_links", ["forked_to_project_id"], {:name=>"index_forked_project_links_on_forked_to_project_id", :unique=>true})
   -> 0.1898s
-- create_table("issues", {:force=>true})
   -> 0.1566s
-- add_index("issues", ["assignee_id"], {:name=>"index_issues_on_assignee_id"})
   -> 0.1786s
-- add_index("issues", ["author_id"], {:name=>"index_issues_on_author_id"})
   -> 0.1787s
-- add_index("issues", ["created_at"], {:name=>"index_issues_on_created_at"})
   -> 0.1788s
-- add_index("issues", ["milestone_id"], {:name=>"index_issues_on_milestone_id"})
   -> 0.3790s
-- add_index("issues", ["project_id"], {:name=>"index_issues_on_project_id"})
   -> 0.1786s
-- add_index("issues", ["title"], {:name=>"index_issues_on_title"})
   -> 0.1788s
-- create_table("keys", {:force=>true})
   -> 0.1806s
-- add_index("keys", ["user_id"], {:name=>"index_keys_on_user_id"})
   -> 0.2009s
-- create_table("merge_requests", {:force=>true})
   -> 0.1454s
-- add_index("merge_requests", ["assignee_id"], {:name=>"index_merge_requests_on_assignee_id"})
   -> 0.1786s
-- add_index("merge_requests", ["author_id"], {:name=>"index_merge_requests_on_author_id"})
   -> 0.1786s
-- add_index("merge_requests", ["created_at"], {:name=>"index_merge_requests_on_created_at"})
   -> 0.1788s
-- add_index("merge_requests", ["milestone_id"], {:name=>"index_merge_requests_on_milestone_id"})
   -> 0.1786s
-- add_index("merge_requests", ["source_branch"], {:name=>"index_merge_requests_on_source_branch"})
   -> 0.1786s
-- add_index("merge_requests", ["source_project_id"], {:name=>"index_merge_requests_on_project_id"})
   -> 0.1785s
-- add_index("merge_requests", ["target_branch"], {:name=>"index_merge_requests_on_target_branch"})
   -> 0.1805s
-- add_index("merge_requests", ["title"], {:name=>"index_merge_requests_on_title"})
   -> 0.1786s
-- create_table("milestones", {:force=>true})
   -> 0.1341s
-- add_index("milestones", ["due_date"], {:name=>"index_milestones_on_due_date"})
   -> 0.1786s
-- add_index("milestones", ["project_id"], {:name=>"index_milestones_on_project_id"})
   -> 0.1786s
-- create_table("namespaces", {:force=>true})
   -> 0.1452s
-- add_index("namespaces", ["name"], {:name=>"index_namespaces_on_name"})
   -> 0.1788s
-- add_index("namespaces", ["owner_id"], {:name=>"index_namespaces_on_owner_id"})
   -> 0.1675s
-- add_index("namespaces", ["path"], {:name=>"index_namespaces_on_path"})
   -> 0.1787s
-- add_index("namespaces", ["type"], {:name=>"index_namespaces_on_type"})
   -> 0.1917s
-- create_table("notes", {:force=>true})
   -> 0.1342s
-- add_index("notes", ["author_id"], {:name=>"index_notes_on_author_id"})
   -> 0.1787s
-- add_index("notes", ["commit_id"], {:name=>"index_notes_on_commit_id"})
   -> 0.1786s
-- add_index("notes", ["created_at"], {:name=>"index_notes_on_created_at"})
   -> 0.1786s
-- add_index("notes", ["noteable_id", "noteable_type"], {:name=>"index_notes_on_noteable_id_and_noteable_type"})
   -> 0.1787s
-- add_index("notes", ["noteable_type"], {:name=>"index_notes_on_noteable_type"})
   -> 0.1896s
-- add_index("notes", ["project_id", "noteable_type"], {:name=>"index_notes_on_project_id_and_noteable_type"})
   -> 0.1897s
-- add_index("notes", ["project_id"], {:name=>"index_notes_on_project_id"})
   -> 0.1897s
-- create_table("projects", {:force=>true})
   -> 0.1453s
-- add_index("projects", ["creator_id"], {:name=>"index_projects_on_owner_id"})
   -> 0.1805s
-- add_index("projects", ["last_activity_at"], {:name=>"index_projects_on_last_activity_at"})
   -> 0.1677s
-- add_index("projects", ["namespace_id"], {:name=>"index_projects_on_namespace_id"})
   -> 0.1675s
-- create_table("protected_branches", {:force=>true})
   -> 0.1343s
-- add_index("protected_branches", ["project_id"], {:name=>"index_protected_branches_on_project_id"})
   -> 0.1897s
-- create_table("services", {:force=>true})
   -> 0.1453s
-- add_index("services", ["project_id"], {:name=>"index_services_on_project_id"})
   -> 0.2009s
-- create_table("snippets", {:force=>true})
   -> 0.1452s
-- add_index("snippets", ["author_id"], {:name=>"index_snippets_on_author_id"})
   -> 0.1788s
-- add_index("snippets", ["created_at"], {:name=>"index_snippets_on_created_at"})
   -> 0.1695s
-- add_index("snippets", ["expires_at"], {:name=>"index_snippets_on_expires_at"})
   -> 0.1676s
-- add_index("snippets", ["project_id"], {:name=>"index_snippets_on_project_id"})
   -> 0.4005s
-- create_table("taggings", {:force=>true})
   -> 0.3453s
-- add_index("taggings", ["tag_id"], {:name=>"index_taggings_on_tag_id"})
   -> 0.2454s
-- add_index("taggings", ["taggable_id", "taggable_type", "context"], {:name=>"index_taggings_on_taggable_id_and_taggable_type_and_context"})
   -> 0.1897s
-- create_table("tags", {:force=>true})
   -> 0.1453s
-- create_table("users", {:force=>true})
   -> 0.1450s
-- add_index("users", ["admin"], {:name=>"index_users_on_admin"})
   -> 0.1787s
-- add_index("users", ["authentication_token"], {:name=>"index_users_on_authentication_token", :unique=>true})
   -> 0.1915s
-- add_index("users", ["email"], {:name=>"index_users_on_email", :unique=>true})
   -> 0.1785s
-- add_index("users", ["extern_uid", "provider"], {:name=>"index_users_on_extern_uid_and_provider", :unique=>true})
   -> 0.1676s
-- add_index("users", ["name"], {:name=>"index_users_on_name"})
   -> 0.1896s
-- add_index("users", ["reset_password_token"], {:name=>"index_users_on_reset_password_token", :unique=>true})
   -> 0.2008s
-- add_index("users", ["username"], {:name=>"index_users_on_username"})
   -> 0.1786s
-- create_table("users_groups", {:force=>true})
   -> 0.1453s
-- add_index("users_groups", ["user_id"], {:name=>"index_users_groups_on_user_id"})
   -> 0.1786s
-- create_table("users_projects", {:force=>true})
   -> 0.1453s
-- add_index("users_projects", ["project_access"], {:name=>"index_users_projects_on_project_access"})
   -> 0.1787s
-- add_index("users_projects", ["project_id"], {:name=>"index_users_projects_on_project_id"})
   -> 0.1805s
-- add_index("users_projects", ["user_id"], {:name=>"index_users_projects_on_user_id"})
   -> 0.1898s
-- create_table("web_hooks", {:force=>true})
   -> 0.1564s
-- add_index("web_hooks", ["project_id"], {:name=>"index_web_hooks_on_project_id"})
   -> 0.1897s
-- initialize_schema_migrations_table()
   -> 0.0004s
-- assume_migrated_upto_version(20130909132950, ["/home/git/gitlab/db/migrate"])
   -> 0.0011s
 
== Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb
2013-09-26T16:04:18Z 27785 TID-619cw INFO: Sidekiq client using redis://localhost:6379 with options {:namespace=>"resque:gitlab"}
 
Administrator account created:
 
login.........admin@local.host
password......5iveL!fe
linux-vuby:~/gitlab>

Logout of the git user back into root user, make sure you are at /home/git/gitlab and copy the init scripts

linux-vuby:~/gitlab> logout
linux-vuby:/ # pwd
/
linux-vuby:/ # cd /home/git/gitlab
linux-vuby:/home/git/gitlab # cp lib/support/init.d/gitlab /etc/init.d/gitlab 
linux-vuby:/home/git/gitlab # chmod +x /etc/init.d/gitlab
linux-vuby:/home/git/gitlab #

Log back in as the git user and change directory to gitlab, then set the gitlab user and email address

linux-vuby:~ # su - git
linux-vuby:~> cd gitlab
linux-vuby:~/gitlab> sudo -u git -H git config --global user.name  "GitLab"
linux-vuby:~/gitlab> sudo -u git -H git config --global user.email "gitlab@$localhost.gitlab"
linux-vuby:~/gitlab>

Get the build information for reference

linux-vuby:~/gitlab> bundle exec rake gitlab:env:info RAILS_ENV=production
 
System information
System:         openSUSE project 12.3
Current User:   git
Using RVM:      no
Ruby Version:   1.9.3p392
Gem Version:    1.8.23
Bundler Version:1.2.3
Rake Version:   10.1.0
 
GitLab information
Version:        6.1.0
Revision:       82f3446
Directory:      /home/git/gitlab
DB Adapter:     mysql2
URL:            http://localhost.gitlab.badzilla.co.uk
HTTP Clone URL: http://localhost.gitlab.badzilla.co.uk/some-project.git
SSH Clone URL:  git@localhost.gitlab.badzilla.co.uk:some-project.git
Using LDAP:     no
Using Omniauth: no
 
GitLab Shell
Version:        1.7.1
Repositories:   /home/git/repositories/
Hooks:          /home/git/gitlab-shell/hooks/
Git:            /usr/bin/git
linux-vuby:~/gitlab>

You need to set the repositories directory to be owned by git:git

linux-vuby:~/gitlab>  sudo chown -R git:git /home/git/repositories/
linux-vuby:~/gitlab>

Fire up gitlab. You may want to do the following activity - checking the build BEFORE you do this. Since I know I'm in good shape, I'm going to run up the application, which gives the following check more to look over.

linux-vuby:~/gitlab> sudo -u git -H bundle exec rake sidekiq:start RAILS_ENV=production
linux-vuby:~/gitlab>

Now check the build.

linux-vuby:~/gitlab> bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...
 
Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes
 
Checking Environment ... Finished
 
Checking GitLab Shell ...
 
GitLab Shell version >= 1.7.1 ? ... OK (1.7.1)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ... can't check, you have no projects
 
Checking GitLab Shell ... Finished
 
Checking Sidekiq ...
 
Running? ... yes
 
Checking Sidekiq ... Finished
 
Checking GitLab ...
 
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ... can't check, you have no projects
Projects have satellites? ... can't check, you have no projects
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.1)
 
Checking GitLab ... Finished
 
linux-vuby:~/gitlab>

Make sure you have switched back to root user, create a virtual host directory for Nginx and download the latest sample configuration file

linux-vuby:/etc/nginx> logout
linux-vuby:~ # mkdir -p /etc/nginx/vhosts.d/
linux-vuby:~ # wget --no-check-certificate https://raw.github.com/gitlabhq/gitlab-recipes/5-0-stable/nginx/gitlab -O /etc/nginx/vhosts.d/gitlab.conf
--2013-10-01 11:12:12--  https://raw.github.com/gitlabhq/gitlab-recipes/5-0-stable/nginx/gitlab
Resolving raw.github.com (raw.github.com)... 185.31.19.133
Connecting to raw.github.com (raw.github.com)|185.31.19.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1210 (1.2K) [text/plain]
Saving to: `/etc/nginx/vhosts.d/gitlab.conf'
 
100%[================================================================>] 1,210       --.-K/s   in 0s      
 
2013-10-01 11:12:12 (95.1 MB/s) - `/etc/nginx/vhosts.d/gitlab.conf' saved [1210/1210]
 
linux-vuby:~ #

Edit this configuration file, making sure your IP address and server name are correctly entered /etc/nginx/vhosts.d/gitlab.conf

listen 127.0.0.1:80 default_server;         # e.g., listen 192.168.1.1:80;
server_name localhost.gitlab.badzilla.co.uk;

Enable and start Nginx

linux-vuby:/etc/nginx/vhosts.d # systemctl enable nginx.service
ln -s '/usr/lib/systemd/system/nginx.service' '/etc/systemd/system/multi-user.target.wants/nginx.service'
linux-vuby:/etc/nginx/vhosts.d # systemctl start nginx.service
linux-vuby:/etc/nginx/vhosts.d #

Ensure the services are automatically started after a reboot

linux-vuby:/etc/nginx/vhosts.d # chkconfig --add mysql
 
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.
 
mysql                     0:off  1:off  2:off  3:on   4:off  5:on   6:off
linux-vuby:/etc/nginx/vhosts.d # chkconfig --add redis
 
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.
 
redis                     0:off  1:off  2:off  3:on   4:off  5:on   6:off
linux-vuby:/etc/nginx/vhosts.d # chkconfig --add gitlab
 
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.
 
gitlab                    0:off  1:off  2:on   3:on   4:on   5:on   6:off
linux-vuby:/etc/nginx/vhosts.d #

Make sure gitlab and nginx is running ok - we've made a load of changes here so always a good idea to restart..and good job I did since Unicorn wasn't running :)

linux-vuby:/etc/nginx/vhosts.d # /etc/init.d/gitlab restart
The Unicorn web was not running, doing nothing.
Stopping Sidekiq job dispatcher.............Sidekiq shut down gracefully.
 
GitLab is not running.
Starting the GitLab Unicorn web server...
Starting the GitLab Sidekiq event dispatcher...
The GitLab Unicorn webserver with pid 1200 is running.
The GitLab Sidekiq job dispatcher with pid 1226 is running.
GitLab and all it's components are up and running.
linux-vuby:/etc/nginx/vhosts.d # /etc/init.d/nginx restart
redirecting to systemctl  restart nginx
linux-vuby:/etc/nginx/vhosts.d #

You are now ready to try out GitLab. Point your web browser at the web address you've been setting in your configuration and you should see the login screen. Enter the default user and password. You will be immediately prompted to change the password and you will then have to log in again.

Once you've logged back in with your new password, you'll see the Dashboard. Success!

Apache / PHP

Next we need to move on to Apache and the PHP projects. We may as well install phpMyAdmin as one of the projects since it uses PHP (obviously!) and it will be useful. In addition, we'll install a clean Drupal build. So let's update the hosts file in preparation and add entries both phpMyAdmin and Drupal. /etc/hosts

127.0.0.1       localhost
127.0.0.1       localhost.gitlab.badzilla.co.uk
127.0.0.1       localhost.phpMyAdmin
127.0.0.1       localhost.drupal.clean.co.uk
127.0.0.1       localhost.www.drupal.clean.co.uk

Let's install the Apache web server. Be sure you are logged in as root.

linux-vuby:/ # zypper install -y apache2
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  apache2 apache2-event apache2-utils libapr-util1 libapr1 
 
The following package is recommended, but will not be installed because it's unwanted (was manually removed before):
  apache2-prefork 
 
5 new packages to install.
Overall download size: 1.2 MiB. After the operation, additional 3.4 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package libapr1-1.4.6-5.1.1.x86_64                        (1/5),  94.3 KiB (222.6 KiB unpacked)
Retrieving: libapr1-1.4.6-5.1.1.x86_64.rpm ...........................................[done (145.7 KiB/s)]
Retrieving package libapr-util1-1.4.1-6.1.1.x86_64                   (2/5),  80.4 KiB (211.3 KiB unpacked)
Retrieving: libapr-util1-1.4.1-6.1.1.x86_64.rpm ....................................................[done]
Retrieving package apache2-utils-2.2.22-10.8.1.x86_64                (3/5),  97.9 KiB (200.0 KiB unpacked)
Retrieving: apache2-utils-2.2.22-10.8.1.x86_64.rpm .................................................[done]
Retrieving package apache2-2.2.22-10.8.1.x86_64                      (4/5), 651.6 KiB (  2.1 MiB unpacked)
Retrieving: apache2-2.2.22-10.8.1.x86_64.rpm .........................................[done (810.0 KiB/s)]
Retrieving package apache2-event-2.2.22-10.8.1.x86_64                (5/5), 259.7 KiB (709.6 KiB unpacked)
Retrieving: apache2-event-2.2.22-10.8.1.x86_64.rpm .....................................[done (1.6 MiB/s)]
(1/5) Installing: libapr1-1.4.6-5.1.1 ..............................................................[done]
(2/5) Installing: libapr-util1-1.4.1-6.1.1 .........................................................[done]
(3/5) Installing: apache2-utils-2.2.22-10.8.1 ......................................................[done]
(4/5) Installing: apache2-2.2.22-10.8.1 ............................................................[done]
Additional rpm output:
/usr/sbin/suexec2: cannot verify root:root 0755 - not listed in /etc/permissions
Updating /etc/sysconfig/apache2...
looking for old 2.0 modules to be renamed...
Done.
 
 
(5/5) Installing: apache2-event-2.2.22-10.8.1 ......................................................[done]
linux-vuby:/ #

Next install phpMyAdmin

linux-vuby:/ # zypper install -y phpmyadmin
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  apache2-mod_php5 apache2-prefork php5 php5-bz2 php5-gd php5-iconv php5-mbstring php5-mcrypt php5-mysql 
  php5-pdo php5-zlib phpMyAdmin 
 
The following recommended package was automatically selected:
  php5-iconv 
 
The following package is recommended, but will not be installed because it's unwanted (was manually removed before):
  php5-zip 
 
12 new packages to install.
Overall download size: 7.9 MiB. After the operation, additional 44.6 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package apache2-prefork-2.2.22-10.8.1.x86_64             (1/12), 251.6 KiB (689.4 KiB unpacked)
Retrieving: apache2-prefork-2.2.22-10.8.1.x86_64.rpm .................................[done (727.2 KiB/s)]
Retrieving package php5-5.3.17-3.4.1.x86_64                         (2/12),   1.2 MiB (  8.9 MiB unpacked)
Retrieving: php5-5.3.17-3.4.1.x86_64.rpm ...............................................[done (1.8 MiB/s)]
Retrieving package php5-zlib-5.3.17-3.4.1.x86_64                    (3/12),  32.3 KiB ( 39.4 KiB unpacked)
Retrieving: php5-zlib-5.3.17-3.4.1.x86_64.rpm ......................................................[done]
Retrieving package php5-pdo-5.3.17-3.4.1.x86_64                     (4/12),  58.7 KiB (131.6 KiB unpacked)
Retrieving: php5-pdo-5.3.17-3.4.1.x86_64.rpm .......................................................[done]
Retrieving package php5-mcrypt-5.3.17-3.4.1.x86_64                  (5/12),  31.7 KiB ( 47.1 KiB unpacked)
Retrieving: php5-mcrypt-5.3.17-3.4.1.x86_64.rpm ....................................................[done]
Retrieving package php5-mbstring-5.3.17-3.4.1.x86_64                (6/12), 415.2 KiB (  2.1 MiB unpacked)
Retrieving: php5-mbstring-5.3.17-3.4.1.x86_64.rpm ......................................[done (2.0 MiB/s)]
Retrieving package php5-iconv-5.3.17-3.4.1.x86_64                   (7/12),  34.3 KiB ( 42.9 KiB unpacked)
Retrieving: php5-iconv-5.3.17-3.4.1.x86_64.rpm .....................................................[done]
Retrieving package php5-gd-5.3.17-3.4.1.x86_64                      (8/12), 113.5 KiB (372.3 KiB unpacked)
Retrieving: php5-gd-5.3.17-3.4.1.x86_64.rpm ........................................................[done]
Retrieving package php5-bz2-5.3.17-3.4.1.x86_64                     (9/12),  28.2 KiB ( 27.3 KiB unpacked)
Retrieving: php5-bz2-5.3.17-3.4.1.x86_64.rpm .......................................................[done]
Retrieving package apache2-mod_php5-5.3.17-3.4.1.x86_64            (10/12),   1.1 MiB (  8.4 MiB unpacked)
Retrieving: apache2-mod_php5-5.3.17-3.4.1.x86_64.rpm ...................................[done (2.3 MiB/s)]
Retrieving package php5-mysql-5.3.17-3.4.1.x86_64                  (11/12),  71.2 KiB (203.8 KiB unpacked)
Retrieving: php5-mysql-5.3.17-3.4.1.x86_64.rpm .....................................................[done]
Retrieving package phpMyAdmin-4.0.5-1.8.1.noarch                   (12/12),   4.6 MiB ( 23.7 MiB unpacked)
Retrieving: phpMyAdmin-4.0.5-1.8.1.noarch.rpm ..........................................[done (2.3 MiB/s)]
( 1/12) Installing: apache2-prefork-2.2.22-10.8.1 ..................................................[done]
( 2/12) Installing: php5-5.3.17-3.4.1 ..............................................................[done]
( 3/12) Installing: php5-zlib-5.3.17-3.4.1 .........................................................[done]
( 4/12) Installing: php5-pdo-5.3.17-3.4.1 ..........................................................[done]
( 5/12) Installing: php5-mcrypt-5.3.17-3.4.1 .......................................................[done]
( 6/12) Installing: php5-mbstring-5.3.17-3.4.1 .....................................................[done]
( 7/12) Installing: php5-iconv-5.3.17-3.4.1 ........................................................[done]
( 8/12) Installing: php5-gd-5.3.17-3.4.1 ...........................................................[done]
( 9/12) Installing: php5-bz2-5.3.17-3.4.1 ..........................................................[done]
(10/12) Installing: apache2-mod_php5-5.3.17-3.4.1 ..................................................[done]
(11/12) Installing: php5-mysql-5.3.17-3.4.1 ........................................................[done]
(12/12) Installing: phpMyAdmin-4.0.5-1.8.1 .........................................................[done]
Additional rpm output:
redirecting to systemctl  try-restart apache2
 
 
linux-vuby:/ #

Now install additional PHP libraries

linux-vuby:/ # zypper install -y php5-ctype
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW package is going to be installed:
  php5-ctype 
 
1 new package to install.
Overall download size: 23.3 KiB. After the operation, additional 14.5 KiB will be used.
Continue? [y/n/?] (y): y
Retrieving package php5-ctype-5.3.17-3.4.1.x86_64                    (1/1),  23.3 KiB ( 14.5 KiB unpacked)
Retrieving: php5-ctype-5.3.17-3.4.1.x86_64.rpm .....................................................[done]
(1/1) Installing: php5-ctype-5.3.17-3.4.1 ..........................................................[done]
linux-vuby:/ #

The best way of installing Drupal is to use the command line utility drush. There are openSUSE 1-click instructions to do this through a web browser, but since this is primarily a command line tutorial, let's keep it consistent. First, install the PHP Pear requirement.

linux-vuby:/ # zypper install -y php5-pear
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW package is going to be installed:
  php5-pear 
 
1 new package to install.
Overall download size: 314.5 KiB. After the operation, additional 2.0 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package php5-pear-5.3.17-3.4.1.noarch                     (1/1), 314.5 KiB (  2.0 MiB unpacked)
Retrieving: php5-pear-5.3.17-3.4.1.noarch.rpm ......................................................[done]
(1/1) Installing: php5-pear-5.3.17-3.4.1 ...........................................................linux-vuby:/ # pear channel-discover pear.drush.org
Adding Channel "pear.drush.org" succeeded
Discovery of channel "pear.drush.org" succeeded
linux-vuby:/ # pear install drush/drush
downloading drush-6.0.0.tgz ...
Starting to download drush-6.0.0.tgz (508,464 bytes)
.............done: 508,464 bytes
install ok: channel://pear.drush.org/drush-6.0.0
linux-vuby:/ #

Ah - and a few more PHP libraries I forgot :)

linux-vuby:/ # zypper install -y php5-curl php5-json php5-soap php5-dom
Loading repository data...
Reading installed packages...
Resolving package dependencies...
 
The following NEW packages are going to be installed:
  php5-curl php5-json php5-soap 
 
4 newpackages to install.
Overall download size: 218.4 KiB. After the operation, additional 470.5 KiB will be used.
Continue? [y/n/?] (y): y
Retrieving package php5-curl-5.3.17-3.4.1.x86_64                     (1/3),  41.9 KiB ( 71.5 KiB unpacked)
Retrieving: php5-curl-5.3.17-3.4.1.x86_64.rpm ......................................................[done]
Retrieving package php5-json-5.3.17-3.4.1.x86_64                     (2/3),  32.0 KiB ( 34.7 KiB unpacked)
Retrieving: php5-json-5.3.17-3.4.1.x86_64.rpm ......................................................[done]
Retrieving package php5-soap-5.3.17-3.4.1.x86_64                     (3/3), 144.5 KiB (364.3 KiB unpacked)
Retrieving: php5-soap-5.3.17-3.4.1.x86_64.rpm ......................................................[done]
Retrieving package php5-dom-5.3.17-3.4.1.x86_64                      (1/1),  68.0 KiB (180.3 KiB unpacked)
Retrieving: php5-dom-5.3.17-3.4.1.x86_64.rpm .......................................................[done]
(1/4) Installing: php5-curl-5.3.17-3.4.1 ...........................................................[done]
(2/4) Installing: php5-json-5.3.17-3.4.1 ...........................................................[done]
(3/4) Installing: php5-soap-5.3.17-3.4.1 ...........................................................[done]
(4/4) Installing: php5-dom-5.3.17-3.4.1 ............................................................[done]
linux-vuby:/ #

Create a database for the clean Drupal build. I elected to use the same database user for this as we created for GitLab. Hardly best practice, but this is a tutorial for localhost only and it won't be used in a production environment.

linux-vuby:/ # mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 29
Server version: 5.5.32 openSUSE package
 
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
 
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
mysql> CREATE DATABASE drupal_clean;
Query OK, 1 row affected (0.00 sec)
 
mysql> GRANT ALL PRIVILEGES ON drupal_clean.* TO 'gitlab'@'localhost' WITH GRANT OPTION;
Query OK, 0 rows affected (0.00 sec)
 
mysql> quit
Bye
linux-vuby:/ #

Now install the clean Drupal build using the drush command line. First download the latest Drupal image, then rename the directory to something useful...

linux-vuby:/ # cd /srv/www/htdocs/
linux-vuby:/srv/www/htdocs # drush dl drupal
Project drupal (7.23) downloaded to /srv/www/htdocs/drupal-7.23.                               [success]
Project drupal contains:                                                                       [success]
 - 3 profiles: minimal, testing, standard
 - 4 themes: garland, bartik, seven, stark
 - 47 modules: drupal_system_listing_incompatible_test, drupal_system_listing_compatible_test,
path, statistics, taxonomy, forum, update, shortcut, toolbar, contact, blog, field_ui, dblog,
overlay, simpletest, menu, aggregator, color, rdf, user, comment, options, text, number, list,
field_sql_storage, field, php, system, block, book, image, trigger, file, locale, tracker,
poll, node, search, help, contextual, profile, dashboard, translation, syslog, openid, filter
 
linux-vuby:/srv/www/htdocs # mv drupal-7.23 drupal-clean
linux-vuby:/srv/www/htdocs # cd drupal-clean
linux-vuby:/srv/www/htdocs/drupal-clean #

...now we start the installation

linux-vuby:/srv/www/htdocs/drupal-clean # drush site-install standard --account-name=admin --account-pass=admin --db-url=mysql://gitlab:gitlab@127.0.0.1/drupal_clean
You are about to DROP all tables in your 'drupal_clean' database. Do you want to continue? (y/n): y
No tables to drop.                                                                             [ok]
Starting Drupal installation. This takes a few seconds ...                                     [ok]
Installation complete.  User name: admin  User password: admin                                 [ok]
linux-vuby:/srv/www/htdocs/drupal-clean #

Change the /srv/www/htdocs/ permissions so everything below is owned by the Apache user and any member of the Apache group has write access

linux-vuby:/srv/www/htdocs/drupal-clean # cd ..
linux-vuby:/srv/www/htdocs # chown -R wwwrun:www *
linux-vuby:/srv/www/htdocs # chmod -R g+w *
linux-vuby:/srv/www/htdocs #

Next we need an Apache configuration. This is best created in httpd.conf.local. Add entries for the two sites.
/etc/apache2/httpd.conf.local

NameVirtualHost *:8050
Listen 8050
 
<VirtualHost *:8050>
    DocumentRoot "/srv/www/htdocs/drupal-clean"
    ServerName localhost.www.drupal.clean.co.uk
    ServerAlias localhost.drupal.clean.co.uk
    RewriteEngine On
    RewriteOptions Inherit
VirtualHost>
 
<Directory /srv/www/htdocs/drupal-clean>
    Options -Indexes +FollowSymLinks
    AllowOverride All
    Order allow,deny
    allow from all
Directory>
 
 
 
<VirtualHost *:8050>
    DocumentRoot "/srv/www/htdocs/phpMyAdmin"
    ServerName localhost.phpMyAdmin
    RewriteEngine On
    RewriteOptions Inherit
VirtualHost>
 
<Directory /srv/www/htdocs/phpMyAdmin>
    Options -Indexes +FollowSymLinks
    AllowOverride All
    Order allow,deny
    allow from all
Directory>

Now we need to tell Apache this configuration file exists so it can be picked up during Apache's start up sequence. Edit the following line in the apache file to reflect this /etc/sysconfig/apache2

APACHE_CONF_INCLUDE_FILES="/etc/apache2/httpd.conf.local"

Edit the same file by adding the Apache php5 module
/etc/sysconfig/apache2

APACHE_MODULES="actions alias auth_basic authn_file authz_host authz_groupfile authz_default authz_user autoindex cgi dir env expires include log_config mime negotiation setenvif ssl userdir  reqtimeout rewrite passenger php5"

Prevent Apache from listening on its normal port 80 by commenting out this value in the listen.conf file. Instead it will use port 8050 as specified in our httpd.conf.local file.
/etc/apache2/listen.conf

#Listen 80

Apache can now be safely started

linux-vuby:/etc/apache2 # /etc/init.d/apache2 start
redirecting to systemctl  start apache2
linux-vuby:/etc/apache2 # ps -ef | grep apach
root      3701     1  0 17:16 ?        00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start
wwwrun    3702  3701  0 17:16 ?        00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start
wwwrun    3704  3701  0 17:16 ?        00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start
wwwrun    3705  3701  0 17:16 ?        00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start
wwwrun    3707  3701  0 17:16 ?        00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start
wwwrun    3708  3701  0 17:16 ?        00:00:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start
root      3710 27868  0 17:17 pts/1    00:00:00 grep --color=auto apach
linux-vuby:/etc/apache2 #

Now we have to tell Nginx about the urls which should be passed on to Apache to deal with. Create the following file and add your domains into the server name line. The filename is arbitrary so long as the extension is .conf
/etc/nginx/vhosts.d/apache-php.conf

server {
   listen 80;
   server_name  localhost.drupal.clean.co.uk localhost.www.drupal.clean.co.uk localhost.phpMyAdmin;
   location / {
       proxy_pass http://127.0.0.1:8050;
    }
    proxy_set_header Host $host;
}

However, you are not quite good to go just yet. I tried this and every single domain rerouted to my gitlab domain. To fix this you need to comment out the listen directive in the gitlab configuration file.
/etc/nginx/vhosts.d/gitlab.conf

  #listen 127.0.0.1:80 default_server;         # e.g., listen 192.168.1.1:80;

Next restart your nginx server.

linux-vuby:/etc/nginx/vhosts.d # /etc/init.d/nginx restart
redirecting to systemctl  restart nginx
linux-vuby:/etc/nginx/vhosts.d #

By opening a browser and pointing to one of your test domains you should see that Nginx has passed on the request to Apache. Here's my phpMyAdmin login screen

Now I check my other domain and lo and behold, the Drupal site installation screen appears.

blog terms

Drupal Linux Apache GitLab nginx PHP

PHP Zend Framework REST Server Tutorial under Apache + Linux

nigel — Sun, 15 Aug 2010 08:28:57 +0000

PHP Zend Framework REST Server Tutorial under Apache + Linux nigel Sun, 15/08/2010 - 09:28

The Zend Framework lends itself to web services due to the bundled classes which come with the Framework. It is ideal both for consuming services (client) and exposing services (server). With this tutorial we'll put together a working REST server using the Framework. If you haven't completed my earlier tutorial on creating a Zend Framework Hello World, you should read it now since we'll be using it as our starting point.

For those who haven't completed the earlier tutorial, make sure you:
1. Create a Zend Framework directory structure ready for a new project. I called mine api;
2. Added a VirtualHost in Apache and restarted the server;
3. Downloaded the latest stable Zend Framework release and installed in the library subdirectory;
4. Created the bootstrapper we used in the previous example.

Ok, we need our service to do something quasi useful to show how our server works. So it'll be a football team server with two methods - 1. to return a list of all English Premier League teams, and 2. to search for a particular football team, or teams. This enables us to show the separation of this 'Business Logic' which will be held in the 'Model' part of the 'MVC' - something we couldn't do in the simplistic Hello World example earlier. In line with convention, our REST server will return the output in XML format.

I'd better duplicate my structure and httpd.conf entries from api to api2 since I should retain api in case I need to refer back. It makes no odds, other than your urls will be slightly different contingent upon which you use.

The first thing we'll do is get a very basic server up and running as a proof of concept. Since we'll be using the built-in Zend_Rest_Server() class, a very basic working server can be up and running in a few minutes.

Proof of Concept

Ok, our very basic service provides a simple "Hello" and "Goodbye" response. First we need the bootstrap file.
api/index.php


    $rdir = realpath(dirname('SCRIPT_NAME'));

    set_include_path($rdir . '/library' . PATH_SEPARATOR . get_include_path());


    try {
        // use Autoloader to load the Zend classes
        // instead of Zend_Loader::loadClass('Zend_Controller_Front');
        // a smarter alternative for larger projects
        require_once('Zend/Loader/Autoloader.php');
        $autoloader = Zend_Loader_Autoloader::getInstance();
        $autoloader->setFallbackAutoloader(true);

        $fcontroller = Zend_Controller_Front::getInstance();

        $fcontroller->throwExceptions(TRUE);
        $fcontroller->setParam('noErrorHandler', TRUE);
        $fcontroller->setControllerDirectory("$rdir/application/controllers");

        $fcontroller->dispatch();

    } catch (Exception $e) {
        $contentType = 'text/html';
        header("Content-Type: $contentType; charset=utf-8");
        print 'An unexpected error occurred:';
        print 'Unexpected Exception: ' . $e->getMessage() . '

';
        print $e->getTraceAsString();
    }
?>

This is practically the same as our previous example, but we have tidied up the class loading by getting a Singleton instance of the autoloader class with Zend_Loader_Autoloader::getInstance();. For larger projects this makes sense rather than continually having to load classes manually with Zend_Loader::loadClass

Next we define the controller code which has similar structure to last time.

class IndexController extends Zend_Controller_Action {

    protected $_server;

    public function init() {

        require_once('Zend/Rest/Server.php');

        $this->_server = new Zend_Rest_Server();
        $this->_helper->viewRenderer->setNoRender();
    }

    public function indexAction() {

        $this->_server->setClass('ServiceSalutations');
        $this->_server->handle();
    }

}



class ServiceSalutations {

    public function sayHello($name) {

        return "Howdee $name, how are you?";
    }

    public function sayGoodbye($name) {

        return "Goodbye $name and have a great day!";
    }
}
?>

The init() function is used to initialise the controller and is called before the preDispatch() hook, so this is the place to instantiate the server. You will also note we are explicitly saying we have no output script for this controller with the $this->_helper->viewRenderer->setNoRender(); call. If you neglect this, the controller will have a look around for a template file to render. In the IndexAction we are defining what our service will look like, and getting a handle to the service. The class ServiceSalutationscontains the two services we are offering - a message to say hello, and one to say goodbye. The REST server will automatically create the XML output, so we are ready to give it a spin! Type the following in your browser:

http://localhost/api2/index.php?method=sayGoodbye&name=badzilla

 generator="zend" version="1.0">
  >
    >Goodbye badzilla and have a great day!>
    >success>
  >
>

http://localhost/api2/index.php?method=junk

 generator="zend" version="1.0">
  >
    >Unknown Method 'junk'.>
  >
  >failed>
>

http://localhost/api2/index.php?method=sayHello

 generator="zend" version="1.0">
  >
    >
      >
        Invalid Method Call to sayHello. Missing argument(s): name.
      >
    >
    >failed>
  >
>

That's the concept proven. However, there are a couple of 'I don't likes' about the solution:
1. I don't like the generator=zend text - firstly it is a distraction and will mean nothing to the end user of my service, and secondly a hacker gleans potentially important information about my server and may target vulnerabilities as a consequence.
2. I don't like the url structure - the method= is cumbersome and again signposts the fact we are using Zend.

Solution

Our fully-blown solution is below. The bootstrap is the same as our Proof of Concept, so I won't reproduce it in case I end up confusing you!
api2/index.php

As earlier. Cut and paste previous code

Next up is the index controller. This does have a few changes to consider.
api2/application/controllers/IndexController.php

class IndexController extends Zend_Controller_Action {

    protected $_server;

    public function init() {

        require_once('Zend/Rest/Server.php');

        $this->_server = new Zend_Rest_Server();
        $this->_server->returnResponse(TRUE);
        $this->_helper->viewRenderer->setNoRender();
    }

    public function indexAction() {

        require_once('application/models/teams.php');
        $this->_server->setClass('ServiceTeams');
        $response = $this->_server->handle();

        header('Content-Type: text/xml');

        // replace generator="zend" with something more appropriate
        echo str_replace('generator="zend"', 'generator="API2"', $response);
    }

}
?>

Some commentary is required here.
$this->_server->returnResponse(TRUE); I got the idea for this my scrutinizing the Zend/Rest/Server.php code. The returnResponse method sets a flag that prevents the server from automatically outputting the xml.
require_once('application/models/teams.php'); Our separation of the business logic from the controller necessitates the inclusion of the model code via a require_once statement.
$this->_server->setClass('ServiceTeams'); We are declaring our service here which will be defined in the model.
header('Content-Type: text/xml'); Since we are no longer reliant upon the Zend server to output the xml, we need to manually set the header.
echo str_replace('generator="zend"', 'generator="API2"', $response); and then output the server's xml but before we do, replace the zend string with API2. This could of course be any string you wish.

The model code contains the available service methods.
api2/application/models/teams.php

class ServiceTeams {

    private $header = '';
    private $teams = array('Arsenal', 'Aston Villa', 'Birmingham City', 'Blackburn Rovers', 'Blackpool', 'Bolton Wanderers', 
                            'Chelsea', 'Everton', 'Fulham', 'Liverpool', 'Manchester City', 'Manchester United', 
                            'Newcastle United', 'Stoke City', 'Sunderland', 'Tottenham Hotspur', 'West Bromwich Albion',
                            'West Ham United', 'Wigan Athltic', 'Wolverhampton Wanderers'
                            );

    public function ListTeams() {

        return $this->_constructOutput();
    }

    public function SearchTeams($search = '') {

        return $this->_constructOutput($search);
    }

    private function _constructOutput($search = '') {

        $count = 0;
        $xml = $this->header;

        $out = '';
        foreach($this->teams as $team) 
            if ($search == '' or strstr($team, $search)) {
                $out .= "" . $team . "";
                $count++;
            }

        $out .= "Found $count teams";

        return simplexml_load_string($xml . $out);        
    }


}
?>

Firstly, please note that a formatting bug is supressing the necessary single quote where $header is defined. If you directly copy this paste for your own app, don't forget to put it back in. Ok, now for some more explanation. You will see that the two publicly available methods are our service definition, SearchTeams and ListTeams. The method _constructOutput will create the xml output for the other two methods. Also worthy of note is the call to the built-in function simplexml_load_string which returns the output to the Zend server in the format it requires.

Finally, we need to use mod_rewrite to rewrite the URL sent to our server so we can live without the annoying method=. To do this, I have created a .htaccess file but you could just as easily put the commands into your httpd.conf file. The beauty of using .htaccess is there is no need for frequent Apache server restarts as we try and debug our statements.
api2/.htaccess

RewriteEngine On
RewriteCond %{QUERY_STRING} !^method=
RewriteCond %{QUERY_STRING} (.*)$
RewriteRule . http://localhost/api2/index.php?method=%1 [L]

We are saying here:
1. Look for any URL that doesn't contain the phrase method= in the query part of the URL;
2. In that circumstance, get the rest of the query string;
3. Add method= ahead of the rest of the URI.

Ok that should do it, so let's give it a spin. Point your web browser at the following locations:
http://localhost/api2/index.php?SearchTeams

>
>Arsenal>
>Aston Villa>
>Birmingham City>
>Blackburn Rovers>
>Blackpool>
>Bolton Wanderers>
>Chelsea>
>Everton>
>Fulham>
>Liverpool>
>Manchester City>
>Manchester United>
>Newcastle United>
>Stoke City>
>Sunderland>
>Tottenham Hotspur>
>West Bromwich Albion>
>West Ham United>
>Wigan Athltic>
>Wolverhampton Wanderers>
>Found 20 teams>
>

http://localhost/api2/index.php?method=SearchTeams&search=City This proves that full URIs are still working ok with the method= present.

>
>Birmingham City>
>Manchester City>
>Stoke City>
>Found 3 teams>
>

http://localhost/api2/index.php?ListTeams

>
>Arsenal>
>Aston Villa>
>Birmingham City>
>Blackburn Rovers>
>Blackpool>
>Bolton Wanderers>
>Chelsea>
>Everton>
>Fulham>
>Liverpool>
>Manchester City>
>Manchester United>
>Newcastle United>
>Stoke City>
>Sunderland>
>Tottenham Hotspur>
>West Bromwich Albion>
>West Ham United>
>Wigan Athltic>
>Wolverhampton Wanderers>
>Found 20 teams>
>

Sorted! Yippee!

blog terms

PHP Apache Linux

Dictionary Attack: How to Block an Entire Country

nigel — Tue, 03 Nov 2009 10:17:46 +0000

Dictionary Attack: How to Block an Entire Country nigel Tue, 03/11/2009 - 10:17

Here's a tip for all website administrators, but you know it already. Please don't think I am high-hatting you, but always remember to check your Apache logs on a regular basis. It is easy to become complacent and neglect this important activity, but if you do you may miss something important - i.e. a systematic attack on your site.

I was casually browsing through my awstats output for one of my sites the other day when I saw something that didn't look correct. The list of pages visited was showing that my site's most popular page was /forum/ucp.php. Now ucp.php is the User Administration Panel login form for the open source bulletin board phpBB3. Uh-oh - someone was repeatedly trying to log into my forum, presumably to post spam. Then I scanned the country list and was shocked to discover that hits from China were practically off the scale. So, circumstantial evidence suggested that the attack may be coming from China.

Further evidence was needed, but out of the box phpBB3 doesn't log failed login attempts so I couldn't be sure exactly what was going on. A quick Google search and I located a phpBB3 mod, rather unsurprisingly called Log Failed Login Attempts In User Log. The author suggests a 5 minute installation. In fact it took me double that, but cut me some slack - it's 18 months since I've applied a phpBB3 mod and I was rusty!

After the mod was installed I left things for 24 hours and checked out the phpBB3 User Log. Sure enough, it was littered with failed log in attempts, and the source was obviously a script which executed every few seconds with a random login name such as steve57857, aixiu8888, fisa697 and Errieharleyminsdavic. Wow! That really is brute force! The good news is the mod also logs the IP address. IP addresses can be looked up from many places, but I use DNSstuff. My suspicions were realised - all the IP addresses originated from China.

But here's the strange thing - whilst all the IP addresses were emanating from China, they were not from the same ISP, and the IP addresses were repeating themselves in the log extremely infrequently. I'm not too sure what that means - perhaps the hacker has access to the top-level China domain.

So, now the evidence had been gathered, it was time to take preventative action. China is not important to my domains so I had no qualms in looking for a solution that would block every allocated Chinese IP address, in fact the way the attack was structured it looked like that would be the best solution anyway.

It is possible to obtain a complete list of Chinese domains from IP Deny. This site can give you a list in Classless Inter-Domain Routing (CIDR) format which looks like:
58.14.0.0/15
58.16.0.0/16
58.17.0.0/17
58.17.128.0/17
58.18.0.0/16
Thankfully Apache can understand this CIDR notation. So somehow I needed to get the entire set of Chinese IP addresses into my .htaccess file. The correct syntax being:

Order Allow,Deny
deny from 58.14.0.0/15
deny from 58.16.0.0/16
deny from 58.17.0.0/17
deny from 58.17.128.0/17
deny from 58.18.0.0/16
.
.
.
Allow from All

You will therefore need to find a decent text editor that can prepend the text deny from at the beginning of each line. I used the Linux command line instead, being an old-school administrator. So I saved the list to /tmp/ips and did:

cat /tmp/ips | awk '{print "deny from "$0}' > /tmp/ipsout

and then copied ipsout into my .htaccess file.

To ensure this works, your Apache httpd.conf must have AllowOverride All directive in the section.

No Apache restart is required. China has now been erased. But remember that domain allocations do change so you should periodically refresh the IP list.

blog terms

Apache