Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 1.95 KB

readme.md

File metadata and controls

35 lines (24 loc) · 1.95 KB
Raw

Docker utility images

About

Bunch of image builders and some workflow stategies where one or another image may be used (should be mentioned that we may use Windows ¯\_(ツ)_/¯ during development):

  1. Run everything on Windows under Vagrant+Virtualbox;
  2. Develop and test on Windows; bundle and ship with Docker;
  3. Run everything on Windows; ship with Docker;

Scenario 1

In that case we have to run application inside web-server + node image with application codebase mounted to the image. I's quite heavy on slow environment and symlinks still don't work, filename limit from Windows is still in place... The only feature is that we might not have node available at the system.

At least we tried. No future.

Scenario 2

Application is running on local machine. All the tests are runned there also. Sounds ok. Application bundling is quite tricky.

First of all we assume that application works behind reverse-proxy. In that case app can handle static files from the bundle and might be reused. Dockerfile should contain instructions for bundling out our app. Configuration takes time (depends on application complexity).

Issue: Docker build fails occasionally on large npm bundles during npm i. But we still can tar/untar modules (from npm-cache or node_modules dir. weird).

If image is bundled shipping works like a charm.

Scenario 3

Scenario 3 is quite similar to the scenario 2. We bundle public assets at the dev environment, server assets at the server environment.

Features:

  • Server-side libraries will be installed proper way;
  • Have to manage dependencies at package.json with care (public libraries should be at devDependencies);
  • Reduce number of needed modules.

Images