From e4645c2dbf90f48a3c449c3ee90ac7a9f6a103e1 Mon Sep 17 00:00:00 2001 From: Sameer Naik Date: Mon, 22 Sep 2014 20:57:04 +0530 Subject: [PATCH] release 7.3.0 --- Changelog.md | 2 +- README.md | 58 ++++++++++++++++++++++++++-------------------------- 2 files changed, 30 insertions(+), 30 deletions(-) diff --git a/Changelog.md b/Changelog.md index 60d57283..b077bc74 100644 --- a/Changelog.md +++ b/Changelog.md @@ -1,6 +1,6 @@ # Changelog -**latest** +**7.3.0** - upgrade to gitlab-ce 7.3.0 - added GITLAB_WEBHOOK_TIMEOUT configuration option - upgrade to gitlab-shell 2.0.0 diff --git a/README.md b/README.md index c181c8e7..3f727e5d 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ Dockerfile to build a GitLab container image. ## Version -Current Version: **7.2.2** +Current Version: **7.3.0** # Hardware Requirements @@ -136,7 +136,7 @@ docker pull sameersbn/gitlab:latest Since version `6.3.0`, the image builds are being tagged. You can now pull a particular version of gitlab by specifying the version number. For example, ```bash -docker pull sameersbn/gitlab:7.2.2 +docker pull sameersbn/gitlab:7.3.0 ``` Alternately you can build the image yourself. @@ -157,7 +157,7 @@ docker run --name='gitlab' -it --rm \ -p 10022:22 -p 10080:80 \ -v /var/run/docker.sock:/run/docker.sock \ -v $(which docker):/bin/docker \ -sameersbn/gitlab:7.2.2 +sameersbn/gitlab:7.3.0 ``` __NOTE__: Please allow a couple of minutes for the GitLab application to start. @@ -189,7 +189,7 @@ Volumes can be mounted in docker by specifying the **'-v'** option in the docker ```bash docker run --name=gitlab -d \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ## Database @@ -239,7 +239,7 @@ The updated run command looks like this. ```bash docker run --name=gitlab -d \ -v /opt/gitlab/data:/home/git/data \ - -v /opt/gitlab/mysql:/var/lib/mysql sameersbn/gitlab:7.2.2 + -v /opt/gitlab/mysql:/var/lib/mysql sameersbn/gitlab:7.3.0 ``` This will make sure that the data stored in the database is not lost when the image is stopped and started again. @@ -264,7 +264,7 @@ To make sure the database is initialized start the container with `app:rake gitl docker run --name=gitlab -it --rm \ -e 'DB_HOST=192.168.1.100' -e 'DB_NAME=gitlabhq_production' -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 app:rake gitlab:setup + sameersbn/gitlab:7.3.0 app:rake gitlab:setup ``` Append `force=yes` to the above command to skip the confirmation prompt. @@ -277,7 +277,7 @@ This will initialize the gitlab database. Now that the database is initialized, docker run --name=gitlab -d \ -e 'DB_HOST=192.168.1.100' -e 'DB_NAME=gitlabhq_production' -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` #### Linking to MySQL Container @@ -333,7 +333,7 @@ docker run --name=gitlab -it --rm --link mysql:mysql \ -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -e 'DB_NAME=gitlabhq_production' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 app:rake gitlab:setup + sameersbn/gitlab:7.3.0 app:rake gitlab:setup ``` **NOTE: The above setup is performed only for the first run**. @@ -345,7 +345,7 @@ docker run --name=gitlab -d --link mysql:mysql \ -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -e 'DB_NAME=gitlabhq_production' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ### PostgreSQL @@ -368,7 +368,7 @@ To make sure the database is initialized start the container with `app:rake gitl docker run --name=gitlab -it --rm \ -e 'DB_TYPE=postgres' -e 'DB_HOST=192.168.1.100' -e 'DB_NAME=gitlabhq_production' -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 app:rake gitlab:setup + sameersbn/gitlab:7.3.0 app:rake gitlab:setup ``` **NOTE: The above setup is performed only for the first run**. @@ -379,7 +379,7 @@ This will initialize the gitlab database. Now that the database is initialized, docker run --name=gitlab -d \ -e 'DB_TYPE=postgres' -e 'DB_HOST=192.168.1.100' -e 'DB_NAME=gitlabhq_production' -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` #### Linking to PostgreSQL Container @@ -438,7 +438,7 @@ docker run --name=gitlab -it --rm --link postgresql:postgresql \ -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -e 'DB_NAME=gitlabhq_production' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 app:rake gitlab:setup + sameersbn/gitlab:7.3.0 app:rake gitlab:setup ``` **NOTE: The above setup is performed only for the first run**. @@ -450,7 +450,7 @@ docker run --name=gitlab -d --link postgresql:postgresql \ -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -e 'DB_NAME=gitlabhq_production' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ## Redis @@ -479,7 +479,7 @@ The image can be configured to use an external redis server instead of starting ```bash docker run --name=gitlab -it --rm \ -e 'REDIS_HOST=192.168.1.100' -e 'REDIS_PORT=6379' \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ### Linking to Redis Container @@ -504,7 +504,7 @@ We are now ready to start the GitLab application. ```bash docker run --name=gitlab -d --link redis:redisio \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ### Mail @@ -526,7 +526,7 @@ The following environment variables need to be specified to get mail support to docker run --name=gitlab -d \ -e 'SMTP_USER=USER@gmail.com' -e 'SMTP_PASS=PASSWORD' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ### SSL @@ -599,7 +599,7 @@ HTTPS support can be enabled by setting the `GITLAB_HTTPS` option to `true`. Add docker run --name=gitlab -d \ -e 'GITLAB_HTTPS=true' -e 'SSL_SELF_SIGNED=true' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` In this configuration, any requests made over the plain http protocol will automatically be redirected to use the https protocol. However, this is not optimal when using a load balancer. @@ -615,7 +615,7 @@ docker run --name=gitlab -d \ -e 'GITLAB_HTTPS=true' -e 'SSL_SELF_SIGNED=true' \ -e 'GITLAB_HTTPS_HSTS_MAXAGE=2592000' -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` If you want to completely disable HSTS set `GITLAB_HTTPS_HSTS_ENABLED` to `false`. @@ -637,7 +637,7 @@ docker run --name=gitlab -d -p 10022:22 -p 10080:80 \ -e 'GITLAB_SSH_PORT=10022' -e 'GITLAB_PORT=443' \ -e 'GITLAB_HTTPS=true' -e 'SSL_SELF_SIGNED=true' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` Again, drop the `-e 'SSL_SELF_SIGNED=true'` option if you are using CA certified SSL certificates. @@ -681,7 +681,7 @@ Let's assume we want to deploy our application to '/git'. GitLab needs to know t docker run --name=gitlab -it --rm \ -e 'GITLAB_RELATIVE_URL_ROOT=/git' \ -v /opt/gitlab/data:/home/git/data \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` GitLab will now be accessible at the `/git` path, e.g. `http://www.example.com/git`. @@ -696,7 +696,7 @@ docker run --name=gitlab -d -h git.local.host \ -v /opt/gitlab/mysql:/var/lib/mysql \ -e 'GITLAB_HOST=git.local.host' -e 'GITLAB_EMAIL=gitlab@local.host' \ -e 'SMTP_USER=USER@gmail.com' -e 'SMTP_PASS=PASSWORD' \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` If you are using an external mysql database @@ -707,7 +707,7 @@ docker run --name=gitlab -d -h git.local.host \ -e 'DB_HOST=192.168.1.100' -e 'DB_NAME=gitlabhq_production' -e 'DB_USER=gitlab' -e 'DB_PASS=password' \ -e 'GITLAB_HOST=git.local.host' -e 'GITLAB_EMAIL=gitlab@local.host' \ -e 'SMTP_USER=USER@gmail.com' -e 'SMTP_PASS=PASSWORD' \ - sameersbn/gitlab:7.2.2 + sameersbn/gitlab:7.3.0 ``` ### OmniAuth Integration @@ -852,7 +852,7 @@ To take a backup all you need to do is run the gitlab rake task to create a back ```bash docker run --name=gitlab -it --rm [OPTIONS] \ - sameersbn/gitlab:7.2.2 app:rake gitlab:backup:create + sameersbn/gitlab:7.3.0 app:rake gitlab:backup:create ``` A backup will be created in the backups folder of the [Data Store](#data-store). You can change that behavior by setting your own path within the container. To do so you have to pass the argument `-e "GITLAB_BACKUP_DIR:/path/to/backups"` to the docker run command. @@ -869,7 +869,7 @@ To restore a backup, run the image in interactive (-it) mode and pass the "app:r ```bash docker run --name=gitlab -it --rm [OPTIONS] \ - sameersbn/gitlab:7.2.2 app:rake gitlab:backup:restore + sameersbn/gitlab:7.3.0 app:rake gitlab:backup:restore ``` The restore operation will list all available backups in reverse chronological order. Select the backup you want to restore and gitlab will do its job. @@ -913,7 +913,7 @@ To upgrade to newer gitlab releases, simply follow this 4 step upgrade procedure - **Step 1**: Update the docker image. ```bash -docker pull sameersbn/gitlab:7.2.2 +docker pull sameersbn/gitlab:7.3.0 ``` - **Step 2**: Stop and remove the currently running image @@ -927,13 +927,13 @@ docker rm gitlab ```bash docker run --name=gitlab -it --rm [OPTIONS] \ - sameersbn/gitlab:7.2.2 app:rake gitlab:backup:create + sameersbn/gitlab:7.3.0 app:rake gitlab:backup:create ``` - **Step 4**: Start the image ```bash -docker run --name=gitlab -d [OPTIONS] sameersbn/gitlab:7.2.2 +docker run --name=gitlab -d [OPTIONS] sameersbn/gitlab:7.3.0 ``` ## Rake Tasks @@ -942,14 +942,14 @@ The `app:rake` command allows you to run gitlab rake tasks. To run a rake task s ```bash docker run --name=gitlab -d [OPTIONS] \ - sameersbn/gitlab:7.2.2 app:rake gitlab:env:info + sameersbn/gitlab:7.3.0 app:rake gitlab:env:info ``` Similarly, to import bare repositories into GitLab project instance ```bash docker run --name=gitlab -d [OPTIONS] \ - sameersbn/gitlab:7.2.2 app:rake gitlab:import:repos + sameersbn/gitlab:7.3.0 app:rake gitlab:import:repos ``` For a complete list of available rake tasks please refer https://github.com/gitlabhq/gitlabhq/tree/master/doc/raketasks or the help section of your gitlab installation.