Skip to content

Add Dockerfile and Docker Compose configuration - #342

Open
suda wants to merge 1 commit into
EVerest:mainfrom
evorada:feat/add-docker
Open

Add Dockerfile and Docker Compose configuration#342
suda wants to merge 1 commit into
EVerest:mainfrom
evorada:feat/add-docker

Conversation

@suda

@suda suda commented Dec 16, 2025

Copy link
Copy Markdown

This PR adds basic Docker configuration for development and hosting the admin panel. The idea is to build it automatically with the release and be able to include it in the everest-demo Docker Compose.

I didn't add any GitHub actions (especially after the recent “Shai Hulud 2” Supply Chain Attack) but please let me know if I should add it too.

Signed-off-by: Wojtek Siudzinski <admin@suda.pl>

@lukas-mertens lukas-mertens left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, thank you for contributing!

Comment thread docker-compose.yml
volumes:
- .:/app
- /app/node_modules
command: sh -c "npm install && npm run dev"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are using pnpm, not npm

Comment thread Dockerfile
COPY . .

# Build the application
RUN npm run build

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are using pnpm, not npm

Comment thread Dockerfile
WORKDIR /app

# Copy package files
COPY package.json package-lock.json* ./

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A package-lock.json should not exist, if working with pnpm

Comment thread docker-compose.yml
everest-admin-panel-dev:
image: node:22-alpine
container_name: everest-admin-panel-dev
working_dir: /app

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this is the best networking setup, as both are running on the same port. Maybe this works with the bridge network you set up, didn't test it.

Also I think having both the dev setup and the demo setup in one docker-compose is likely not what we want. I feel it would be a better idea to have e.g. a separate docker-compose.dev.yml for the people that need it? Otherwise docker compose up just starts both...

Also I don't know if one really wants to use a docker compose for development, having a devcontainer would be the better alternative in my opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants