This pull request addresses the need highlighted in the issue for enhancing the customization process within Frappe Docker deployments. The current method of manually modifying the compose.yaml file for custom applications, as described in the issue, can potentially lead to challenges in version control and file integrity.
To alleviate this, I propose the introduction of environment variables, including CUSTOM_IMAGE, CUSTOM_TAG, PULL_POLICY, HTTP_PUBLISH_PORT and HTTPS_PUBLISH_PORT, which users can leverage to customize their deployments seamlessly. This approach not only simplifies the customization process but also enhances the maintainability and consistency of Frappe Docker configurations.
By incorporating this feature, users can define their custom image names and tags directly through environment variables, facilitating smoother deployments without compromising the integrity of configuration files. Further details and discussions regarding the necessity and implementation of this enhancement are available in the associated issue.
Details
This pull request addresses the need highlighted in the issue for enhancing the customization process within Frappe Docker deployments. The current method of manually modifying the
compose.yaml
file for custom applications, as described in the issue, can potentially lead to challenges in version control and file integrity.To alleviate this, I propose the introduction of environment variables, including
CUSTOM_IMAGE
,CUSTOM_TAG
,PULL_POLICY
,HTTP_PUBLISH_PORT
andHTTPS_PUBLISH_PORT
, which users can leverage to customize their deployments seamlessly. This approach not only simplifies the customization process but also enhances the maintainability and consistency of Frappe Docker configurations.By incorporating this feature, users can define their custom image names and tags directly through environment variables, facilitating smoother deployments without compromising the integrity of configuration files. Further details and discussions regarding the necessity and implementation of this enhancement are available in the associated issue.