Skip to content

Conversation

@digitaladapt
Copy link

I've been updating my personal setup to have everything managed in containers, for easier management, and thought I'd share.

The main piece is the Dockerfile, along with a very minor tweak to the express.js to allow it to gracefully close when requested.

I've included a simple walk-through and example config files to make it as straight forward as possible.

@vercel
Copy link

vercel bot commented May 24, 2024

@digitaladapt is attempting to deploy a commit to the github readme stats Team on Vercel.

A member of the Team first needs to authorize it.

@LockedThread
Copy link

Just what I was looking for! Thanks.

maxh33 added a commit to maxh33/github-readme-stats that referenced this pull request Dec 12, 2025
Addresses common Docker deployment issues with detailed solutions:

Problem Areas Covered:
- Import path resolution errors (../../themes vs ../themes)
- Missing dependencies in package.json
- Docker build context configuration
- Node version mismatches (Node 18 vs 22)
- Husky/pre-commit hook conflicts in containers
- Entry point and working directory issues

Solutions Include:
- Root cause analysis for each issue
- Before/after code examples
- Step-by-step fix instructions
- File structure diagrams
- Testing verification steps

Value:
- Helps users with ANY Docker setup
- Real-world tested solutions
- Complements existing Docker efforts (PR anuraghazra#3775)
- Reduces support burden with comprehensive troubleshooting

Testing:
- Production deployment verified
- No container restart loops
- Comprehensive troubleshooting solutions
@maxh33
Copy link

maxh33 commented Dec 12, 2025

Hi @digitaladapt! 👋

I've been working on deploying github-readme-stats via Docker to solve the rate-limiting issues on my VPS, and your PR has been incredibly helpful as a reference.

I just submitted PR #4695 with comprehensive Docker troubleshooting documentation that might complement your work here. Through production deployment, I encountered and documented solutions for several common issues:

  • Import path resolution (../../themes vs ../themes)
  • Missing dependencies in package.json
  • Node version mismatches
  • Husky/pre-commit hook conflicts
  • Build context configuration

Production Enhancements I've Implemented:

If you're interested, I'd be happy to collaborate or share approaches for:

  1. Multi-stage build optimization - Separating deps/builder/runner stages for smaller images
  2. Security hardening - Non-root user (UID 1001), read-only filesystem, minimal capabilities
  3. Resource constraints - CPU/memory limits for production stability
  4. Health checks - Integrated with Traefik for zero-downtime deployments
  5. Environment variable configuration - Making configs portable (no hardcoded domains/ports)
  6. CI/CD pipeline - GitHub Actions workflow for automated build/deploy

My deployment is currently running in production successfully (all 242 tests passing, auto-restarts via Watchtower, SSL via Traefik).

Would you be interested in incorporating any of these patterns into your PR? Or would you prefer I submit enhancements separately after your base Docker support merges? Happy to collaborate however works best!

Thanks for pioneering Docker support for this project! 🚀

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.

3 participants