[Feature] Publish frontend Docker images to GHCR

[raphaelbahat]

场景描述

Currently, users who want to run GithubStarsManager need to clone the entire repository and build the frontend Docker image locally from the Dockerfile. This creates several friction points:

1. Users must have Git installed and clone the full repository
2. Build time overhead for every new deployment
3. Inconsistent builds across different environments
4. Difficult to track which frontend version is running without referencing git tags

By publishing frontend images to GHCR, users can simply reference the image in their docker-compose configuration, similar to how the backend is already published.

建议解决方案

Publish frontend Docker images to GHCR (GitHub Container Registry) and update the docker-compose.yml configuration:

1. Set up GitHub Actions workflow to build and push frontend images to ghcr.io/amintacccp/github-stars-manager-frontend on every release or on push to main
2. Tag images with version numbers and latest tag
3. Update docker-compose.yml to reference the published image instead of building locally:

   frontend:
     image: ghcr.io/amintacccp/github-stars-manager-frontend:${FRONTEND_IMAGE_TAG:-latest}
     ports:
       - "8080:80"
     depends_on:
       - backend
     restart: unless-stopped

4. Document the new deployment approach for users

附加说明

Related Work:

• Backend images are already published to GHCR at ghcr.io/amintacccp/github-stars-manager-server
• The frontend Dockerfile is at the repository root and builds successfully

Benefits:

• Simplified deployment for users - no need to clone repository
• Faster deployments with pre-built images
• Better version tracking and reproducibility
• Aligns with container best practices
• Consistent with existing backend deployment model

[AmintaCCCP]

Hi @raphaelbahat 👋

This is now shipped! PR #240 has been merged and the frontend image is published to GHCR alongside the backend. Here's how to use it.

Image location

ghcr.io/amintacccp/github-stars-manager-frontend

Available tags (same scheme as the backend):

• latest — newest build from main
• 1.2.3, 1.2, 1 — semver tags from v* releases
• sha-<commit> — pin to an exact commit

Multi-arch: both linux/amd64 and linux/arm64 are built.

Option 1 — Docker Compose (recommended)

The published image is already wired into docker-compose.yml, so you no longer need to clone/build:

docker-compose up -d

To customize secrets and pin versions, create a .env file in the project root:

API_SECRET=my-strong-secret
ENCRYPTION_KEY=my-encryption-key
BACKEND_IMAGE_TAG=latest    # pin backend image version
FRONTEND_IMAGE_TAG=latest   # pin frontend image version
# BACKEND_HOST=backend:3000 # target for the frontend's /api proxy (default: backend:3000)
# RESOLVER=127.0.0.11       # DNS resolver for backend re-resolution (default: Docker DNS)

Then docker-compose up -d picks them up automatically. The app is available at http://localhost:8080.

Option 2 — Run the frontend standalone

docker pull ghcr.io/amintacccp/github-stars-manager-frontend:latest

docker run -d -p 8080:80 \
  -e BACKEND_HOST=host.docker.internal:3000 \
  --name github-stars-manager \
  ghcr.io/amintacccp/github-stars-manager-frontend:latest

App: http://localhost:8080

Configuration

Variable	Default	Description
BACKEND_HOST	backend:3000	Upstream the frontend proxies /api/ to. Standalone: use your backend's reachable address, e.g. host.docker.internal:3000 on Docker Desktop, or the container IP/host on a shared network.
RESOLVER	127.0.0.11	DNS resolver used to re-resolve BACKEND_HOST at runtime (so a recreated backend won't leave /api/ stuck on a stale IP). On non-Docker platforms (Kubernetes, ECS, custom networks) set this to your cluster/platform DNS IP.
FRONTEND_IMAGE_TAG	latest	(Compose only) which image tag to pull.

The Nginx config is rendered at container startup from nginx.conf.template via envsubst, substituting BACKEND_HOST and RESOLVER.

Full docs are in DOCKER.md. Thanks for the great suggestion! 🎉