Docker deployment setup

[ramonechen]

This pull request standardizes Compose, Dockerfile, and .dockerignore file formats to be in line with deployment setups of the API and SIS scraper repositories.

Changes include:

• Using an inclusion pattern in .dockerignore instead of the old exclusion pattern
• Adding clarifying comments to the Dockerfile
• Repurposing the Dockerfile for production environments
• Adding an image build and publish workflow
• Enhancing the Compose file by explicitly defining a container name, image pull and restart policies
• Adding a top-level comment to the Compose file explaining how to start the development environment
• Enforcing a npm version of 11.12.x to comply with the project's package-lock.json

[Copilot]

Pull request overview

Standardizes the project’s Docker/Compose setup (and related CI) to match the deployment conventions used in other CARPI repositories.

Changes:

• Updates docker-compose.yml with clearer dev-environment instructions and more explicit container/image settings.
• Adjusts Dockerfile to pin npm (per package-lock.json) and adds clarifying build/run comments.
• Adds a GitHub Actions workflow to build/publish the Docker image, and switches .dockerignore to an allowlist approach.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
docker-compose.yml	Renames service and clarifies dev workflow; adds container/image policies and updates volume mounts.
Dockerfile	Pins npm version, changes workdir to /site, and documents build/run steps.
.github/workflows/image-publish.yml	Adds a reusable workflow call to build/push an image to GHCR on main pushes.
.dockerignore	Switches to allowlist-based build context to standardize what’s sent to Docker builds.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.