chore: deploy docs with a docker container

[KaelWD]

This reverts commit 1e28f5a.

Zeit claims to support node 10.15, but only installs up to 10.7

[codecov]

Codecov Report

Merging #7929 into next will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             next    #7929      +/-   ##
==========================================
+ Coverage   85.64%   85.65%   +0.01%     
==========================================
  Files         333      333              
  Lines        9091     9091              
  Branches     2414     2414              
==========================================
+ Hits         7786     7787       +1     
+ Misses       1212     1211       -1     
  Partials       93       93

Impacted Files	Coverage Δ
packages/vuetify/src/components/VSelect/VSelect.ts	94.13% <0%> (+0.36%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 674b03f...6df4e2f. Read the comment docs.

[DRoet]

Idk how well Zeit uses the docker cache, but usually its better to first copy over the package.json / .lock file and install the dependencies and then copy over the rest of the source files, instead of a wildcard copy.

something like:

FROM mhart/alpine-node:12

COPY package.json yarn.lock ./

RUN yarn
RUN yarn build

COPY . .

EXPOSE 8095

CMD ["yarn", "start"]

This way it won't have to install all the dependencies if it is just the source files that are changing.

[KaelWD]

ah k, it wasn't any slower than the default node deploy so I didn't bother seeing if it could be improved.

This would only work for the initial yarn install stage though, and would require a bit of maintenance to make sure all the packages and postinstall hooks are copied correctly what with the whole monorepo thing