We're excited to announce a powerful new addition to DeployHQ: the ability to deploy only configuration files. This feature offers a streamlined and efficient way to manage your application's settings without the need to deploy the entire codebase.
Why Deploy Only Configuration Files?
- Faster Deployments: By isolating configuration changes, you can deploy updates more frequently and with minimal downtime.
- Improved Security: Sensitive configuration data can be managed separately, reducing the risk of exposure.
- Simplified Workflow: Streamline your deployment process by focusing on configuration changes.
How It Works:
- Create a Configuration File: Define your application's settings in a dedicated configuration file (e.g.,
.env
,config.yml
). - Configure Deployment: In your DeployHQ project settings, specify the configuration file and the target deployment environment.
- Deploy Configuration: Trigger a deployment using our dashboard, API, or CLI. Only the configuration file will be deployed.
Key Benefits:
- Flexibility: Choose between dashboard, API, or CLI deployment methods based on your preferences.
- Granular Control: Deploy specific configuration changes without affecting the entire codebase.
- Integration: Easily integrate this feature into your existing deployment workflows.
Get Started Today:
To start using this new feature, log in to your DeployHQ account and explore the project settings. If you're new to DeployHQ, sign up for a free trial to experience the power of our platform.
We're excited to hear your feedback and see how you'll leverage this new feature to improve your deployment process!