Skip to main content

Allow deployment of just config files

Sometimes you need to update and redeploy a config file and doing a full deployment seems unnecessary.

Status: Completed4 comments

Log in to comment and vote

Comments4

  • Giacomo Iacovelli

    •

    Oct 9, 2024

    This is a nice feature but maybe it could be a good idea to have the option to really just deploy the config file in an atomic deployment instead of creating a new release folder. This may be a problem if you need some old releases as backup and the new release with this minor change drops the older releases. Or if some of the release paths are stored as temporary paths in a database you always have to clear/regenerate these also it is just a minor change in config.

    • Facundo@DHQ

      Team•

      Oct 15, 2024

      Well, I got your point, and I think it’s valid, but it depends. By creating an entire new release I think it’s more clear, in the sense that we can think about that release as a unity. Still, thanks for the feedback!

  • Viktor@DHQ

    •

    Sep 26, 2024

    Good news!

    We’ve recently released a new DeployHQ version that implements this Config file deployment feature!

    This feature creates a new deployment to your selected server group, which only transfers the existing config files that have been assigned to that server group. For all intents and purposes, the config file transfer works in the same manner as it does during a standard deployment, but without the hassle of a full deployment process.

    Feel free to test the feature out, and reach out to us if any issue arises! More information on this feature can be found here: https://www.deployhq.com/support/deployments/config-file-deployments

    Cheers!

    • Ralf Wiechers

      •

      Sep 26, 2024

      Love the improvement