Add detailed instructions how to update GDK with webpack

CHANGELOG.md

@@ -8,6 +8,41 @@ features.
 - Add webpack process to Procfile configure it within gitlab.yml !237
+    For existing GDK installations, manual action is required to update GDK.
+    Assuming `origin` is the upstream repo, do the following:
+
+    1. First, update the CE/EE repo:
+
+        ```
+        cd <gitlab-ce-dir>
+        git pull origin master
+        bundle install && npm purge && npm install
+        bundle exec rake webpack:compile
+        ```
+
+    1. Pull the new GDK changes:
+
+        ```
+        cd <gdk-dir>
+        git pull origin master
+        ```
+
+    1. Make sure postgres is running:
+
+        ```
+        cd <gdk-dir>
+        gdk run db
+        ```
+
+    1. Then, **open a separate terminal window** and update GDK along with all its
+       components:
+
+        ```
+        cd <gdk-dir>
+        gdk reconfigure
+        gdk update
+        ```
+
 ## 2016-10-31
 - Add root check to catch root move problems. Requires gem 0.2.3 or

[Grzegorz Bizon]

Do we really need to compile assets to make it work in development environment? As far as I remember assets are being served from the memory. What do you think @mikegreiling?

[username-removed-636429]

Yeah, the rake task isn't necessary in development... The error you saw asking if you had run rake webpack:compile is output by the webpack-rails gem when it can't find the manifest. Simply having the webpack running and configured should prevent this.

[username-removed-636429]

Actually all of the steps above are performed when you run gdk update anyway, so this part shouldn't be necessary.

[Grzegorz Bizon]

Do we need to run databases in order to invoke gdk reconfigure?

[Achilleas Pipinellis]

Not for configure, but for update.

[username-removed-128633]

FYI I just had to run:

gdk run db

# in another tab
gdk update