feat: Add Docker support with multi-stage build for easy deployment

[Copilot]

This PR adds comprehensive Docker support to the TypeScript-based Telegram bot project, enabling easy containerized deployment.

🐳 What's Added

Multi-stage Dockerfile

• Build stage: Uses Node.js 20 alpine image to compile TypeScript source code
• Production stage: Creates optimized runtime image with only production dependencies
• Optimized size: Final image is only 210MB
• Secure build: Handles SSL certificate issues in Docker environment

Comprehensive .dockerignore

Excludes unnecessary files from build context:

• node_modules/, dist/, .git/
• Environment files (.env, .env.*)
• IDE files, logs, and temporary files
• Documentation and development files

Updated Documentation

• Replaced "Coming soon" Docker section with complete deployment instructions
• Added Docker feature to developer experience section
• Provided example commands with required environment variables

🚀 Usage

# Build the Docker image
docker build -t unthread-telegram-bot .

# Run the container with environment variables
docker run -d \
  --name unthread-bot \
  -e TELEGRAM_BOT_TOKEN=your_bot_token \
  -e UNTHREAD_API_KEY=your_api_key \
  -e UNTHREAD_CHANNEL_ID=your_channel_id \
  -e DATABASE_URL=your_postgres_url \
  unthread-telegram-bot

✅ Testing

• Docker build completes successfully
• Container starts and loads the application correctly
• Proper error handling when environment variables are missing
• Production dependencies only (no devDependencies in final image)
• Correct file structure with compiled JavaScript in /app/dist/

🔧 Technical Details

Build Process:

1. Install all dependencies (including devDependencies)
2. Compile TypeScript source code using yarn build
3. Create production image with only runtime dependencies
4. Copy compiled JavaScript from build stage

Environment Handling:

• Temporarily disables the preinstall script during Docker build to avoid SSL conflicts
• Configures npm/yarn registries for Docker environment compatibility
• Uses HTTP registry fallback for reliable package installation

This implementation follows Docker best practices with multi-stage builds, minimal attack surface, and optimized layer caching for faster subsequent builds.

Closes the Docker deployment requirement and enables easy containerized deployments across different environments.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[warengonzaga]

@copilot I can see that the Dockerignore is bloated, can you ensure that we only ignore to fit with our Node.js application project.

[Copilot]

@copilot I can see that the Dockerignore is bloated, can you ensure that we only ignore to fit with our Node.js application project.

I've streamlined the .dockerignore file by removing 69 unnecessary lines that were specific to frameworks not used in this project (Next.js, Nuxt.js, Gatsby, Serverless, etc.). The file now focuses only on Node.js/TypeScript essentials needed for this Telegram bot project. Commit: 71ab6e2

[warengonzaga]

All good, just waiting for the PR #23 to add markdown callouts for additional warning for users.

[warengonzaga]

@copilot I can see that the Dockerignore is bloated, can you ensure that we only ignore to fit with our Node.js application project.

I've streamlined the .dockerignore file by removing 69 unnecessary lines that were specific to frameworks not used in this project (Next.js, Nuxt.js, Gatsby, Serverless, etc.). The file now focuses only on Node.js/TypeScript essentials needed for this Telegram bot project. Commit: 71ab6e2

Help improve Copilot by leaving feedback using the 👍 or 👎 buttons

@copilot can you bump the version accordingly?

[Copilot]

@copilot I can see that the Dockerignore is bloated, can you ensure that we only ignore to fit with our Node.js application project.

I've streamlined the .dockerignore file by removing 69 u...

I've bumped the version from 1.0.0-beta.1 to 1.0.0-beta.2 in package.json to reflect the Docker feature addition. Commit: 147c40d

[Copilot]

Pull Request Overview

This PR adds Docker support to the TypeScript-based Telegram bot project, enabling containerized deployment through a multi-stage Dockerfile and improved documentation.

• Introduces a multi-stage Dockerfile to separate build and production stages with secure and optimized image creation.
• Updates package version and enhances the README with Docker build and run instructions alongside security recommendations.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updated version to reflect new release including Docker support changes.
README.md	Added Docker instructions, a docker-compose tip, and a security notice.
Dockerfile	Introduces a multi-stage build with adjustments to dependency installation.
.dockerignore	Updated to exclude unnecessary files from the Docker build context.

Comments suppressed due to low confidence (1)

README.md:211

• [nitpick] Consider providing an example or a link to a sample docker-compose.yml file to guide users when opting for the docker-compose deployment method.

docker-compose up -d

[warengonzaga]

@copilot can you apply this suggestion?
#22 (comment)

[Copilot]

@copilot can you apply this suggestion?
#22 (comment)

I've applied the suggestion by refactoring the approach to use the DOCKER_BUILD=true environment variable instead of inline sed modifications. The preinstall script now conditionally runs npx only-allow yarn only when not in a Docker build environment, maintaining package.json integrity. Commit: bad476e

[warengonzaga]

LGTM!