🚄 Job van der Voort 🚀 · e67c757d
--- a/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+++ b/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+And the hard work shouldn't even include setting up GitLab. [See below]() for
+the full video, in which we install GitLab and ship a full app, from idea to
+production, in under Y minutes.
+
+This month's Most Valuable Person ([MVP](https://about.gitlab.com/mvp/)) is ***MVP_USER*** ***CONTRIBUTION_OF_MVP_USER***.
+Thanks ***MVP_USER_FIRST_NAME***!
+
+<!--more-->
+
+## Installing GitLab to deploying to Production in Y minutes
+
+< FULL VIDEO>
+
+## Auto Deploy
+
+> [Documentation link](link)
--- a/source/posts/2016-12-22-gitlab-8-15-released.html.md
+++ b/source/posts/2016-12-22-gitlab-8-15-released.html.md

 > [Documentation link](link)

-## Improved Bitbucket Importer
+## Improved BitBucket Importer
--- a/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+++ b/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+Working together with your container scheduler, GitLab happily spins up several
+(dynamic) environments on request for your projects. Be that for review apps
+or a staging or production environment.
+Traditionally, getting direct access to these environments has been a little
+painful. And that's a shame: it's very useful to quickly try something in a
+live environment to debug a problem, or just to experiment.
+
+With the web terminal, this has become extremely easy. Just visit the
+environments page in your project and click on the terminal button.
+GitLab will SSH into the instance for you and allow you to do anything
+you would be able to do from your local instance.
+
+![Web Terminal in GitLab 8.15](/images/8_15/terminal_gif.gif){: .shadow}
+
+In the demonstration at [5:18](https://youtu.be/m0nYHPue5RU?t=318) we show you
+give you a quick peek at the web terminal. We can't wait to see how you'll
--- a/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+++ b/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+automatically deploy your application using Docker to your container scheduler.
+The cool thing about this is that this immediately leverages Review Apps,
+meaning you can see it working before even merging the merge request!
+
+![Auto deploy in GitLab 8.15](/images/8_15/auto_deploy.png)
+
+This is as close as you can get to one-click deploys, while exposing what
+is happening and having all this version-controlled, ready
+to collaborate and iterate on.
+
+See [1:42](https://youtu.be/m0nYHPue5RU?t=102) in the video for a quick demo of
+Auto Deploy, as it is available in GitLab 8.15.
+
+For this first iteration, we ship Auto Deploy with a template for deploying to an external OpenShift cluster. We use [Herokuish](https://github.com/gliderlabs/herokuish) and Heroku Buildpacks to
+package your application into a Docker Image that then is deployed to
+Kubernetes on Openshift. We want to add support for more container
--- a/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+++ b/source/posts/2016-12-22-gitlab-8-15-released.html.md 0 → 100644
+
+The current version of PostgreSQL we are packaging (9.2.18) is slowly
+approaching its EOL. Due to the [PostgreSQL versioning policy](https://www.postgresql.org/support/versioning/),
+upgrades between major releases require downtime and the use of the `pg_upgrade` tool.
+
+For this purpose, we are packaging the newest available PostgreSQL version (9.6.1).
+We are also introducing `gitlab-ctl pg-upgrade` tool which should make this
+transition as painless as possible.
+When upgrading to GitLab 8.14, this *action will not be run automatically*.
+This will allow you to plan the database upgrade downtime.
+
+After version 9.0 is released, we plan on setting the PostgreSQL version 9.6 as
+default so please make sure that you plan your upgrade before that release.
+We're expecting to ship GitLab 9.0 on or after February 22nd.
+
+> [Read more about database upgrade in our docs](https://docs.gitlab.com/omnibus/maintenance/README.html#upgrade-postgresql-database)