Ensure we're using at least pgsql 9.1 for extensions to work during gitlab:setup
Update apache2.4 for forward secrecy/no compression
Adds forward secrecy and disables SSL/TLS compression which is potentially exploitable.
…-server 9.3 as extenions are not supported in 8.x and therefore bundle exec rake gitlab:setup RAILS_ENV=production would fail otherwise
Update Ciphers Nginx The current suggested Ciphers do not qualify anymore as completely safe, see for instance [here.](https://community.qualys.com/blogs/securitylabs/2013/03/19/rc4-in-tls-is-broken-now-what) This updates the ciphers, following [Remy's advise](https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html).
Changed logging in and out again to instead recommend sourcing the .bash_profile
change in gitlab-shell/config.yml
Because later in this recipe it is suggested to set port 80 to 443 (ssl) redirection I recommend to advice user to set https in config.yml file. It takes me some time to find this as problem when accessing gitlab api (gitlabhq/gitlabhq#3483)
…tent Remove installer for 4.0 since it is a security risk
…mpty directories since it is not clear which OS's have documentation.
Importing is important and should be a toplevel thing.
Fixed SELinux modifications for Apache
The boolean httpd_enable_homedirs isn't needed. httpd_read_user_content is enough (http://serverfault.com/a/461738). All file context rules can be applied in one transaction (http://danwalsh.livejournal.com/41593.html).
[Guide] Update Gitlab Stable to to 6-7-stable
Added FreeBsd Installation Bumps / Troubleshooting Guide
[Guide Update] Gitlab 6.6 - CentOS 6.5 Installation
Fixed some typos