Hi, we strongly need an options to give access to separate config files for a user In one project can be production and development config files, which we should separate access between of users

Completed

ACL User managment , who can acess to config

Vladyslav LTD

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

Allow deployment of just config files

Pete Heaney

As a DeployHQ user, I want to manage my SSH keys globally across all my projects, so that I don't have to upload the same key to multiple projects.

Support Global SSH Keys

Facundo@DHQ

Make build configuration configurable per server. At the moment it is annoying to deploy an updated version of an app to a staging site, as you need to change the build config for the whole project, which then blocks any deployments to the production site.

In Review

Build configuration per server

Matty Forth

As a DeployHQ user, I want to be able to log in to DeployHQ using Single Sign-On (SSO) with various identity providers (e.g., Google, Okta, etc.), so that I can simplify my login process and reduce the risk of credential breaches.

Add SSO (Google, Okta, etc)

As a DeployHQ user I would like to be able to manage servers in a global context, so they can be used across multiple projects, so that I can easily apply consistent settings for deployment and build processes.

Support for global servers

Robert Venning

As a user of DeployHQ, I want to be able to execute SSH commands on my servers without transferring files, so that I can perform tasks like running scripts, checking system status, or configuring settings efficiently.

Allow SSH-Only Deployments (without file transfer)

As a DeployHQ user, I want to integrate DeployHQ with AWS ElasticBeanstalk, so that I can deploy my applications to ElasticBeanstalk environments directly from DeployHQ

Add integration: AWS ElasticBeanstalk

As a DeployHQ user, I want to integrate Digital Ocean with DeployHQ, so that I can deploy my applications directly to Digital Ocean droplets from within DeployHQ.

Add Integration: Digital Ocean

It would be handy to securely create and store custom environment variables on a server basis to be used during SSH commands and Config files. We are currently restricted to only what is available: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.deployhq.com/support/projects/variables">https://www.deployhq.com/support/projects/variables</a> This would then avoid need to create individual config files per server. Instead, we only need one and ensure the environment variables are set. This is a pretty common setup in other CI/CD providers (ie: github, gitlab, bitbucket, etc)

Custom Server Environment Variables

David Burleson

I can see it is possible to schedule a deployment to run monthly, but this only allows you to select a calendar day of the month (1st of each month etc) to run the deployment on.We’d love to be able to select a day of the week with this schedule e.g. run on the first Monday of the month, to ensure deployments go out during our support hours.

Ability to select day of the week for monthly scheduled deployments

Josh Hinton

As a software engineer, I want to be able to transfer tar files efficiently for deployments, so that I can reduce deployment time and improve overall efficiency.

Tar File Transfer for Accelerated Deployments

As a DeployHQ user,I want to be able to integrate rsync with my deployments, so that I can efficiently transfer and synchronize files between my local machine and remote servers during the deployment process.

Add Integration: rsync

Our creditcard bill is getting larger by the month with all our services. It would be really nice if we could have SEPA / IBAN as a payment method. Not sure what PSP integration you are using but I believe Stripe has this feature.

Add SEPA as a billing method

Sjoerd Gal

As a project manager or software engineer, I want to be able to control the deployment availability for individual projects, so that I can manage the risk associated with new deployments and ensure that they are only released to production when they are ready.

Allow to configure deployment availability per project

As a DeployHQ user, I want to have the option to log in using my existing social accounts (Google, GitHub, Bitbucket, etc.), so that I can quickly and easily access my DeployHQ account without having to create and remember yet another password.

Add Social Logins (Google, Github, Bitbucket, etc)

I may have missed it somewhere but is there a way to track/see how long each ssh command in a deployment took without adding custom outputs to each command. This will help debugging slow areas of the deployment process

SSH command timing

Gareth Venn

As a DeployHQ user with multiple projects, I want to be able to group projects into folders, so that I can better organize and manage my projects.

Allow to group projects in folders

The Build Pipeline page currently allows you to add, remove, and reorder commands. However, it does not provide an option to toggle a command's enabled or disabled status, which would be extremely helpful. For example, if you have commands that you want to turn on or off occasionally, such as linting, reporting, or cache clearing, users currently have to delete and manually re-add the command to achieve this. A simple button to toggle the enabled or disabled status would be fantastic.

Option to toggle commands in the build pipeline

Elliott Mangham

Something I’ve requested from the DHQ team a few months ago, but it’d be ideal if commit hashes were checked on scheduled deploys to prevent regular usage of build minutes.This option was added after some discussion with the support team but it doesn’t seem to have the effect needed because we still see regular deploys, daily, despite the latest commit hash not changing in weeks.<img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/01926661-23f3-7f4a-9b9a-bfa4f9ca5f76.png" data-width="100%" data-align="left">The use case for this is that we have a lot of projects that all need manual deployment to production which we’re trying to phase out with “rolling releases” so verified and tested pull requests can be merged and deployment can be handle at a set time, daily, instead of a regular task.

DeployHQ

Have something to say?