https://www.deployhq.com/blog/project-templates

In Deploy v1 we offered preset templates that could be applied to a project.

https://www.deployhq.com/blog/unlock-seamless-deployments-announcing-deployhq-s-heroku-integration

Streamline your application deployments to Heroku with ease.

https://www.deployhq.com/support/network-agent-errors/destination-address-not-allowed

When attempting to configure, or deploy to a server using the DeployHQ agent, you may run into the following … error: ``` Destination address not allowed ``` This happens when you're trying to connect to … a server that isn't permitted to connect via the Agent. … In order to connect to another machine in your network, you'll need to add its local IP address to `~ … After changes are made to agent.access, you'll need to restart the agent.

https://www.deployhq.com/support/common-server-errors/deployment-key-errors

You may run into the following error when trying to configure a server in your project: ``` Command … failed to execute: Warning: Permanently added 'repo-host.com,1.2.3.4' (ECDSA) to the list of known hosts … contact it to obtain a list of branches to deploy from. … The later would happen if you'd uploaded your own custom private key to the project. … To resolve this, you'll just need to head to the **Configuration** area in your project, copy the public

https://www.deployhq.com/support/build-errors/command-not-found

If you're fetching specific tools to run on your code, you'll need to ensure the appropriate executable … directory is added to your local PATH. … Adding a simple command to your build process should allow the build to find the correct executable. … For example, if you're using `npm install` to retrieve a specific tool, just add your node_modules/bin … directory to your PATH, like so: ```bash PATH=$PATH:/data/node_modules/.bin ``` Anything you

https://www.deployhq.com/support/common-deployment-errors/server-host-key-changed

You may see an error similar to below when you come to run a deployment to a particular project: ` … Alternatively, it could be indicative of someone trying to hijack the connection to your server. ` … `` ``` Error connecting to server your-server. … As the error explains, you can navigate to your server's properties page via the **Servers & Groups**

https://www.deployhq.com/support/build-errors/update-composer-build-pipeline

In order to be able to use Composer 2.8.8 in the Build Pipeline, the workaround for the time being would … /composer --version ``` We are going to update the version in the default container from 2.6.6 to

https://www.deployhq.com/support/common-deployment-errors/general-sftp-write-failure

Is this case, there is no way to tell a specific reason for the failure. … However, it will most likely be one of the following: * Renaming a file to a name of a file that already … * Moving a remote file to a different filesystem. * Uploading a file to a full filesystem.

https://www.deployhq.com/support/build-errors/grunt-not-found

following error whilst running your build commands: ``` Grunt not found ``` This means grunt needs to … be installed, You'll need to add the following to your build commands: ``` npm install --quiet grunt-cli

https://www.deployhq.com/support/common-deployment-errors/npm-no-such-file-or-directory

enoent ENOENT: no such file or directory ``` This is due to npm not being able to find the file, … usually you will need to cd into the correct directory first, before running the command.