-
Notifications
You must be signed in to change notification settings - Fork 552
Docker
We have Docker images published into:
More specifically:
-
https://hub.docker.com/r/everco/gauzy-api - Gauzy API Image. Pull it with
docker pull everco/gauzy-api. -
https://hub.docker.com/r/everco/gauzy-webapp - Gauzy UI Image. Pull it with
docker pull everco/gauzy-webapp.
To build such images on each release (push to our master branch), we are using relevant Github Action.
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 a website (from the root of mono-repo):
docker build . -t gauzy-webapp -f .deploy/webapp/Dockerfile
To run website:
docker run -p 127.0.0.1:4200:4200/tcp --env API_BASE_URL=http://localhost:3000 --env API_HOST=10.0.0.1 gauzy-webapp
Note: replace API_HOST value with IP address or hostname of the API host and API_BASE_URL value with external URL for API, i.e. where API will be accessible for browser. Leave as above if you just want to run it locally for testing.
To build API (from the root of mono-repo):
docker build . -t gauzy-api -f .deploy/api/Dockerfile
To run API:
docker run -p 127.0.0.1:3000:3000/tcp gauzy-api
docker run --rm -it --entrypoint=sh name-of-image
For example:
docker run --rm -it --entrypoint=sh ghcr.io/ever-co/gauzy-api
To just run the same image without entrypoint:
docker run --rm -it ghcr.io/ever-co/gauzy-api
Currently, you need to setup a .env file containing all the necessary environment variables. You can use the existing .env.sample.
Set up .env using cp .env.sample .env.