-
Notifications
You must be signed in to change notification settings - Fork 0
/
Dockerfile
78 lines (64 loc) · 1.93 KB
/
Dockerfile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
######################################
# Stage: nodejs dependencies and build
FROM node:18.15.0-alpine3.17 AS builder
WORKDIR /webapp
ADD package.json .
ADD package-lock.json .
# use clean-modules on the same line as npm ci to be lighter in the cache
RUN npm ci && \
./node_modules/.bin/clean-modules --yes --exclude exceljs/lib/doc/ --exclude mocha/lib/test.js --exclude "**/*.mustache"
# Adding UI files
ADD public public
ADD shared shared
ADD nuxt.config.js .
ADD config config
ADD contract contract
# Build UI
ENV NODE_ENV production
RUN npm run build && \
rm -rf dist
# Adding server files
ADD server server
ADD shared shared
ADD upgrade upgrade
ADD contract contract
# Check quality
ADD .gitignore .gitignore
ADD test test
RUN npm run lint
RUN npm run test
RUN npm audit --omit=dev --audit-level=critical
# Cleanup /webapp/node_modules so it can be copied by next stage
RUN npm prune --production
RUN rm -rf node_modules/.cache
##################################
# Stage: main nodejs service stage
FROM node:18.15.0-alpine3.17
MAINTAINER "contact@koumoul.com"
RUN apk add --no-cache dumb-init
WORKDIR /webapp
# We could copy /webapp whole, but this is better for layering / efficient cache use
COPY --from=builder /webapp/node_modules /webapp/node_modules
COPY --from=builder /webapp/nuxt-dist /webapp/nuxt-dist
ADD nuxt.config.js nuxt.config.js
ADD public/static public/static
ADD server server
ADD shared shared
ADD config config
ADD contract contract
ADD upgrade upgrade
# Adding licence, manifests, etc.
ADD package.json .
ADD README.md BUILD.json* ./
ADD LICENSE .
ADD nodemon.json .
# configure node webapp environment
ENV NODE_ENV production
ENV DEBUG db,upgrade*
# the following line would be a good practice
# unfortunately it is a problem to activate now that the service was already deployed
# with volumes belonging to root
#USER node
VOLUME /webapp/data
EXPOSE 8080
CMD ["dumb-init", "node", "--max-http-header-size", "64000", "server"]