🎯 An Open-Source NodeJS-based Content Management System with a fully customizable API. You can save time and effort by creating production-ready Node.js APIs in hours rather than weeks. 🚀
Developers are faced with the task of launching a development environment that has different software packages of certain versions. Fortunately, Docker solves this problem in the modern development world.
🐳 Creating a new `Dockerfile` tf NPM was your ☠️, then please use the following 👇
# FROM node:16-alpine
## Installing libvips-dev for sharp Compatability
# RUN apk update && apk add build-base gcc autoconf automake zlib-dev libpng-dev nasm bash vips-dev
FROM node:16
## Installing libvips-dev for sharp Compatability
RUN apt-get update && apt-get install libvips-dev -y
ARG NODE_ENV=development
ENV NODE_ENV=${NODE_ENV}
WORKDIR /opt/
COPY ./package.json ./package-lock.json ./
ENV PATH /opt/node_modules/.bin:$PATH
RUN npm install
WORKDIR /opt/app
COPY ./ .
RUN npm run build
EXPOSE 1337
CMD ["npm", "run", "develop"]
Quick tour of Dockerfile: 👇
🐳 To get started, let's take a quick tour of Dockerfile: 👇
Initially, we’ll use node:16 (2.62 GB) or node:16-alpine (1.53~1.91 GB) as our base image.
We’ll install some libraries, like libvips-dev for sharp compatibility, with -y, so say yes to everything.
The node environment AVG will be set to development by default so we don’t have to provide this each time.
The ENV allows us to override it if we want to switch from development to production.
We’ll define our file paths and whatnot in the /opt WORKDIR working folder inside our container.
We copy package.json and yarn.lock (or package-lock.json if you’re using npm) into our work directory. Docker caches each layer, so doing this first will speed up our build process.
Docker then knows where to find our node_modules
In case of network problems or a bit of slow internet, we will set a large timeout 600000 to allow extra time.
Afterwards, yarn install installs all dependencies.
Then we change the directories to /opt/apps
Next, we copy the project we created in step 1, cms-backend, into this folder.
We then run yarn build to build our MEAN project.
Finally, we expose port 1337 and tell Docker to run yarn develop
.dockerignore 👇
🐳 Docker Ignore: Create a file called `.dockerignore`: 👇
.tmp/
.cache/
.git/
build/
node_modules/
data/
✍️ These folders in .dockerignore will be skipped ⛔️ by Docker 🐳 since they are not necessary.
✍️ We are currently using an SQLite database, which is always inside the container. Whenever we stop a container, we lose all changes. Using docker-compose, we can use a Postgres database and run multiple instances of Docker if needed.
🐳 In the root of the project, create a file called `docker-compose.yml`. Due to the YAML format, spacing matters, so I've used spaces rather than tabs 👇
services - We are defining two services cms and cmsDB
cms - The name of the service we defined
container_name - The name of the container. You can call it whatever you want.
build - Telling cms to build the image in our project folder ..
image - The image name we want to build
restart - Unless we STOP or take down the container, it will keep restarting.
env_file - Providing a .env file containing the environmental variables we should keep secret.
environment - Here we define all the variables we want to use. Our .env file will have $[THISISOURNAME] as a placeholder.
volumes - mounting files into the container. Now this could be ./:/opt/app, but we might want to develop locally and just run our development server locally we are binding folders and some files to not bind node_modules There is some info about that here.
ports - What ports we want to expose. Note: You can change the left side to another port, such as 8080:1337, but remember that the right side needs to be 1337, which is the port inside the container where CMS is running.
networks - Set up a docker network so that our containers can communicate together. The Docker-Network tells Docker that before running the cms container, we need to run the postgresDB container first. This saves us some errors when we start the CMS container without a database.
Similarly, we give Postgres a name, but we use the official postgres:12.0-alpine image instead of building it ourselves. In addition, we are creating a volume called cms-data to hold our database.
✍️ When installing Docker Desktop for MacOS, docker-compose is also automatically installed; however, for Linux, you must separately install it.
Facilitate and undertake communication, collaboration, integration and automation to improve efficiency and workflow across different specialist IT teams.
