Add Portainer stack configuration with Traefik support #2255
+777
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds complete Portainer deployment support for Fizzy: - docker-compose.portainer.yml: Production-ready stack with MySQL and Fizzy - Configured for Traefik reverse proxy with automatic SSL - Uses external networks: traefik_public and digital_network - Includes health checks and proper dependencies - Persistent volumes for database and storage - .env.portainer.example: Environment variables template - All required variables documented with examples - SMTP configuration for email support - VAPID keys setup for web push notifications - Easy to copy and customize - README-PORTAINER.md: Complete deployment guide in Portuguese - Step-by-step setup instructions - Secret generation commands - DNS and SSL configuration - Troubleshooting section - Backup and update procedures - .gitignore: Allow .env*.example files to be committed The GitHub Actions workflow (publish-image.yml) already publishes images to ghcr.io/basecamp/fizzy automatically on main branch pushes, so no manual Docker builds are needed.
Simplifies the deployment process by eliminating the need to run the Fizzy container just to generate secrets. Changes: - scripts/generate-secrets.sh: Automated secret generator - Generates SECRET_KEY_BASE using OpenSSL (no container needed!) - Generates VAPID keys for Web Push notifications - Optionally creates .env.portainer file automatically - User-friendly interactive prompts - scripts/README.md: Documentation for the scripts - README-PORTAINER.md: Updated deployment guide - Highlights the new easy script-based approach - Keeps container-based method as fallback - Clarifies which values are mandatory vs optional - .env.portainer.example: Improved template - Added helpful comments pointing to the script - Clearer instructions for generating secrets Before: Users had to download and run the Fizzy container to generate secrets After: Just run ./scripts/generate-secrets.sh - simple and fast!
Resolves the "Services.fizzy.depends_on must be a list" error by properly configuring the stack for Docker Swarm mode. Changes to docker-compose.portainer.yml: - Remove container_name (not supported in Swarm) - Change depends_on from condition syntax to simple list (Swarm doesn't support service_healthy condition) - Move restart policies to deploy.restart_policy - Move Traefik labels to deploy.labels (Swarm requirement) - Add deploy.replicas configuration - Change MYSQL_HOST from "fizzy_db" to "tasks.db" (Swarm DNS) - Add traefik.docker.network label for Swarm mode - Reorder services (db first, then fizzy) Changes to README-PORTAINER.md: - Add warning about Docker Swarm mode requirement - Add docker swarm init instructions - Add section explaining Swarm mode benefits - Document Swarm-specific differences (DNS, labels, etc) - Add useful Swarm commands (stack services, service logs, scale) This stack now works correctly with Portainer in Swarm mode with overlay networks (digital_network and traefik_public).
Simplifies stack to only Fizzy service, connecting to user's existing MySQL instance instead of deploying its own database. Changes to docker-compose.portainer.yml: - Remove db service completely - Remove fizzy_db_data volume - Change MYSQL_HOST to use environment variable (default: mysql) - Make all MySQL connection settings configurable via env vars - Remove depends_on (no longer needed) Changes to .env.portainer.example: - Add MySQL External Database section - Document MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASSWORD - Add helpful comments for different MySQL deployment scenarios (Swarm service, Docker container, remote server) Changes to README-PORTAINER.md: - Update prerequisites to mention external MySQL requirement - Add MySQL configuration section in step 2 - Add important notes about MySQL network and permissions - Update troubleshooting section: - Remove references to fizzy_db service - Add comprehensive MySQL connectivity debugging steps - Add network configuration help - Add MySQL permissions verification - Update Swarm commands (remove db service logs) This configuration allows users to: - Use their existing MySQL instance - Avoid running duplicate MySQL containers - Keep database management separate from application
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds complete Portainer deployment support for Fizzy:
docker-compose.portainer.yml: Production-ready stack with MySQL and Fizzy
.env.portainer.example: Environment variables template
README-PORTAINER.md: Complete deployment guide in Portuguese
.gitignore: Allow .env*.example files to be committed
The GitHub Actions workflow (publish-image.yml) already publishes images to ghcr.io/basecamp/fizzy automatically on main branch pushes, so no manual Docker builds are needed.