Skip to content

Conversation

@VargaJoe
Copy link
Contributor

@VargaJoe VargaJoe commented Oct 3, 2025

Summary

Adds Docker containerization to enable easy deployment and development setup.

What's Added

  • Dockerfile: Single-stage build with yarn snapp start
  • docker-compose.dev.yml: Development setup with hot reload
  • docker-compose.prod.yml: Production setup without volumes
  • .dockerignore: Optimized build context
  • DOCKER.md: Complete setup documentation
  • GitHub Actions: Automated Docker image builds to DockerHub

Usage

# Development (hot reload)
docker-compose -f docker-compose.dev.yml up -d

# Production
docker-compose -f docker-compose.prod.yml up -d

- Add Dockerfile for SenseNet client application
- Add docker-compose.dev.yml for development with hot reload
- Add docker-compose.prod.yml for production deployment
- Add .dockerignore for optimized builds
- Add .env.example for environment configuration

Usage:
- Development: docker-compose -f docker-compose.dev.yml up -d
- Production: docker-compose -f docker-compose.prod.yml up -d
- Add GitHub Actions workflow for Docker image builds
- Builds and pushes to DockerHub with smart tagging
- Triggers on pushes to docker-containerization branch
- Triggers on PRs to develop, main, and sn-auth-package-extraimprovements
- Safely skips build if no Dockerfile exists
- Uses branch-based and SHA-based tags for versioning
- Fix invalid tag format causing build failure
- Use proper suffix/prefix for SHA tags
- Ensure Docker tag compliance
- Skip draft PRs to avoid duplicate builds
- Only trigger PR builds when PR is ready for review
- Maintain push-based builds for active development
- Remove standalone SHA tags to prevent DockerHub clutter
- Keep clean branch names and branch+SHA tags for useful scenarios
- Maintain manageable tag strategy for long-term development
- Removed multi-stage Dockerfile complexity
- Updated documentation to match single Dockerfile approach
- Both dev and prod modes use 'yarn snapp start'
- Development uses volume mounts for hot reload
- Production uses built-in code without volumes
- Simplified and cleaner Docker setup
@VargaJoe VargaJoe marked this pull request as ready for review October 3, 2025 18:07
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