Moved yarn build

Author: David Zuckerman

Dockerfile

@@ -88,7 +88,7 @@ ENV NODE_PATH=/usr/local/yarn/node_modules
 # yet, so if the build fails before the `bundle install` step below, you
 # will need to override the default command when troubleshooting the buggy
 # image.
-CMD ["rails", "server", "-b", "0.0.0.0"]
+CMD ["bundle", "exec", "rails", "server", "-b", "0.0.0.0"]
 
 # =============================================================================
 # Target: development
@@ -134,7 +134,7 @@ RUN bundle install
 # re-install.
 COPY --chown=$APP_USER:$APP_USER . .
 
-RUN yarn install --cwd /usr/local/yarn 
+RUN yarn install --cwd /usr/local/yarn
 
 # =============================================================================
 # Target: production
@@ -169,8 +169,11 @@ RUN bundle install --local
 
 # TODO: Figure out why jsbundling-rails doesn't invoke `yarn build`
 #       *before* Sprockets reads app/assets/config/manifest.js
-RUN yarn install --cwd /usr/local/yarn 
+#RUN yarn install --cwd /usr/local/yarn 
+WORKDIR /usr/local/yarn
+RUN yarn build
 
+WORKDIR /opt/app
 # Pre-compile assets so we don't have to do it after deployment.
 # NOTE: dummy SECRET_KEY_BASE to prevent spurious initializer issues
 #       -- see https://github.com/rails/rails/issues/32947