Explains:
- How Dokploy manages ports vs docker-compose ports
- Why to use 'expose' instead of 'ports' in Dokploy
- Port conflict resolution
- SSL/HTTPS port flow (443 → 8080 internal)
- Recommended configurations for Dokploy vs manual deployment
This helps users understand why we use expose instead of ports mapping in docker-compose.yml when deploying to Dokploy.
Port changes:
- HTTP_PORT: 8088 → 8080 (default Frappe port)
- All documentation updated to reflect port 8080
- GitHub Actions tests updated to port 8080
- SSL works correctly with standard port 8080 in Dokploy
Reason:
- Port 8080 is the standard Frappe frontend port
- Dokploy SSL/HTTPS works better with default port
- Consistent with Frappe conventions
Files updated:
- README.md
- dokploy/README.md
- dokploy/QUICKSTART.md
- dokploy/DEPLOYMENT.md
- dokploy/SSL_SETUP.md
- dokploy/SUMMARY.md
- dokploy/CHANGELOG.md
- dokploy/CHECKLIST.md
- dokploy/docker-compose.yml
- .github/workflows/build-dokploy.yml
SSL/HTTPS:
- Dokploy handles SSL termination on port 443
- Internal communication uses port 8080
- HTTPS redirect automatic
- Let's Encrypt auto-renewal
Critical fix:
- Dockerfile: Do not delete node_modules folders (socket.io needed at runtime)
- Only remove .git folders and Python cache
- Preserve all npm packages for WebSocket functionality
New documentation:
- dokploy/TROUBLESHOOTING.md: Common issues and solutions
* WebSocket host not found
* socket.io module not found
* Frontend restart loop
* Site not found errors
This fixes:
- Frontend restart loop
- WebSocket container crashes
- socket.io MODULE_NOT_FOUND errors
WebSocket requires socket.io, redis, socket.io-redis packages at runtime.
These must NOT be deleted in Dockerfile cleanup.
- Introduced `MINIMAL_SETUP_COMPLETE.md` detailing the minimal and optimized deployment of Frappe ERPNext with 5 core applications.
- Updated `build-dokploy.yml` to reflect port changes and added verification steps for installed applications.
- Enhanced performance metrics showcasing significant improvements in build time and resource usage.
- Updated various configuration files and documentation to align with the new minimal setup, emphasizing fast deployment and automatic SSL configuration.
- Removed unnecessary applications (LMS, Builder, Print Designer, Wiki) from `apps.json`, `Dockerfile`, and `docker-compose.yml` for a streamlined deployment.
- Updated installation command in `docker-compose.yml` to reflect the new minimal setup.
- Enhanced documentation in `QUICKSTART.md`, `README.md`, and `SUMMARY.md` to clarify the core applications included and their functionalities.
- Added new `SSL_SETUP.md` for detailed SSL configuration instructions.
- Changed the Helpdesk application branch in `apps.json` and `Dockerfile` to `v1.14.0`, ensuring compatibility with Frappe v15.
- Removed version declaration from `docker-compose.prod.yml` and `docker-compose.yml` for cleaner configuration.
- Revised RUNTIME_FIX.md to provide clearer guidance on the removal of the CRM application due to compatibility issues with Frappe v15.
- Added detailed troubleshooting steps and alternative solutions to assist users in resolving runtime errors.
- Updated README.md to reflect these changes and improve overall application compatibility documentation.
- Enhanced README.md to clarify the inclusion of built-in CRM features in ERPNext and updated the application list.
- Introduced RUNTIME_FIX.md to document the removal of the CRM application due to compatibility issues with Frappe v15, detailing the error encountered and providing alternative solutions.
- Updated deployment strategies and troubleshooting steps to ensure successful application setup.
- Added additional file types to the exclusion list for the end-of-file-fixer and prettier hooks, including shell scripts, YAML files, and Docker-related files.
- This enhances the linting process by preventing unnecessary checks on specific file types.
- Expanded the exclusion patterns for YAML files in the check-yaml and prettier hooks to include overrides and GitHub workflows.
- Enhanced the codespell hook's ignore words list for better spell-checking accuracy.
- Introduced HRMS and Helpdesk applications, increasing total applications to 9.
- Updated .pre-commit-config.yaml to refine linting rules and exclude patterns.
- Removed shfmt hook due to unavailability in GitHub Actions.
- Enhanced documentation in APPS_UPDATE_COMPLETE.md to reflect new applications and linting changes.
- Updated APPS_INFO.md to include new applications (HRMS, Helpdesk) and revised compatibility details.
- Adjusted the installation command in docker-compose.yml to include the new applications and remove deprecated ones.
- Enhanced documentation for clarity on application features and installation processes.
- Corrected YAML syntax in `.pre-commit-config.yaml` to fix alias errors.
- Updated application branches in `apps.json` and `Dockerfile` to reflect actual existing branches for Frappe apps.
- Introduced new applications (HRMS, Helpdesk) and removed incompatible ones.
- Enhanced documentation in `APPS_INFO.md` and `README.md` to reflect changes and ensure clarity on application compatibility.
- Updated application branches in `apps.json` and `Dockerfile` to use `version-15` for compatibility with Frappe v15.
- Removed incompatible applications (Twilio Integration, ERPNext Shipping) and documented changes in `APPS_INFO.md`.
- Introduced a new `.pre-commit-config.yaml` for linting and formatting with specific exclusions.
- Fixed linting issues in `install.sh` and added shellcheck directives for better script validation.
- Created `LINT_FIX_COMPLETE.md` to summarize linting fixes and application updates.
- Added new GitHub Actions workflows for automatic tagging and release creation.
- Updated Dockerfile to fix the path for `apps.json` during the build process.
- Introduced a comprehensive release guide and version tracking file.
- Enhanced README with new badges for build status and latest release.
- Documented troubleshooting steps and deployment processes in the new release guide.
- Added Dokploy setup documentation including Dockerfile, Docker Compose configurations, and automation scripts.
- Integrated 9 applications (ERPNext, CRM, LMS, Builder, Print Designer, Payments, Wiki, Twilio Integration, ERPNext Shipping) into a single image.
- Implemented health checks, production optimizations, and CI/CD workflows with GitHub Actions.
- Created comprehensive guides for environment variables, deployment, and modular setup.
- Introduced a checklist for deployment and a changelog for tracking changes.
* Remove hardcoded amd64 images. This slows down development on ARM Macs significantly.
* Do not use prebuilt bench image as it may be outdated or not available as an ARM build.
The source image is in this repo anyway.
* Use the prebuilt image by default.
* update version of postgress in compose.yml file
* fix(postgres): upgrade to v14 for COMMIT AND CHAIN support
---------
Co-authored-by: abhirock74 <abhishek.suvaidyam@gmail.com>
