Deploying new asset pipeline

ansible/playbooks/deploy_app.yml

@@ -20,6 +20,7 @@
         -d '{"version": "{{ lookup('pipe', 'date "+%Y-%m-%d %H:%M:%S"') }}"}'
 
     - name: Cleanup static assets before compression
+      run_once: yes
       connection: local
       file:
         state: absent
@@ -84,7 +85,7 @@
       git:
         repo: https://github.com/samuelclay/NewsBlur.git
         dest: /srv/newsblur/
-        version: pipeline
+        version: master
       register: pulled
       tags:
         - static

ansible/playbooks/setup_app.yml

@@ -1,7 +1,7 @@
 ---
 - name: SETUP -> app containers
   hosts: web
-  serial: "50%"
+  # serial: "50%"
   vars_files:
     - ../env_vars/base.yml
   vars:

ansible/roles/repo/tasks/main.yml

@@ -21,4 +21,4 @@
   git:
     repo: https://github.com/samuelclay/NewsBlur.git
     dest: /srv/newsblur/
-    version: pipeline
+    version: master

docker/newsblur_deploy.Dockerfile

@@ -24,4 +24,4 @@ RUN	npm -g install yuglify
 RUN apt-get clean
 
 WORKDIR /srv/newsblur
-CMD python manage.py collectstatic --no-input --clear -v 3 -l
+CMD python manage.py collectstatic --no-input --clear -v 1 -l

templates/maintenance_off.html

@@ -85,7 +85,7 @@
                         <img src="/media/img/logo_512.png" class="logo">
                         <h1>NewsBlur is in <span class="error404">maintenance mode</span></h1>
                         <div class="description">
-                            <p>This is a unique maintenance mode. This is only for deploying the new front-end asset packager we're switching to (here's the merge on GitHub). It's a bit messy though, since there is a brief moment when switching from the old to the new that can be in a buggy, liminal state of using part of one system and part of another. So to avoid that I'm just going to throw up a maintenance page for a quick minute.</p>
+                            <p>This is a unique maintenance mode. This is only for deploying the new front-end asset packager we're switching to (<a href="https://github.com/samuelclay/NewsBlur/commit/26dd479714812b14791834f4f7854a3068e37a1c" target="window">here's the merge on GitHub</a>). It's a bit messy though, since there is a brief moment when switching from the old to the new that can be in a buggy, liminal state of using part of one system and part of another. So to avoid that I'm just going to throw up a maintenance page for a quick minute.</p>
                             <p>To pass the time, <a href="http://mltshp.com/popular">check out what's popular on MLTSHP</a>.</p>
                         </div>
                     </div>