-
Notifications
You must be signed in to change notification settings - Fork 466
Docker
Ruslan Konviser edited this page Jul 30, 2022
·
2 revisions
We have Docker images published into:
How does it work?
- To build such images on each release (push to
master
branch), we are using relevant Github Action. - See also this folder to understand how our docker containers are built.
- In addition, you can review Github Action workflow to see what env vars we pass to the docker containers running in k8s.
Run docker-compose up -d --build
to build the Docker images and run in detached mode(-d
).
Run docker-compose -f docker-compose.demo.yaml up -d
to use the latest image from GitHub. You may have to run docker-compose -f docker-compose.demo.yaml pull
to update your images.
To build API (from the root of mono-repo):
docker build . -t ever-api -f .deploy/api/Dockerfile
To run API:
docker run -p 127.0.0.1:5500:5500/tcp ever-api
docker run --rm -it --entrypoint=sh name-of-image
For example:
docker run --rm -it --entrypoint=sh ghcr.io/ever-co/ever-api
To just run the same image without specifying an entrypoint
:
docker run --rm -it ghcr.io/ever-co/ever-api
- Currently, you need to setup a
.env
file containing all the necessary environment variables. - You can use the existing
.env.template
from/packages/core
folder. Set up.env
usingcp .env.template .env
and adjust required env vars values.