https://www.deployhq.com/support/build-pipelines/deploybuild-dot-yaml

This works in a very similar way to the `.deployignore` concept - just create your file, commit it to … Out the box, we support being able to define build cache files, language versions, and commands. … , don't need to have access to the DeployHQ UI to do so … then modified as you go - again without the need to log in to the UI. … When adding specific language versions, you only need to specify the major version, i.e.

https://www.deployhq.com/guides/v0

v0 makes it easy to spin up a UI and preview it on Vercel. … call-to-action button and a headline … You can also import an existing GitHub repository and use v0 to make changes to it. … No need to copy-paste code into a separate editor. … Deploy a v0 App to DeployHQ Static Hosting](https://www.deployhq.com/blog/deploy-v0-app-to-deployhq-static-hosting

https://www.deployhq.com/support/build-errors/cannot-install-saas-globally

Due to the way permissions work inside our build environment, the user that we use for user build commands … does not have the ability to install packages globally. … To prevent this error from happening, all you'll need to do is remove the `-g` flag from `npm install … adjust it to use the locally installed package. … - Updating your build script to use a package manager like `npm run` or `yarn` to

https://www.deployhq.com/guides/firebase-studio

use but not subject to any SLA. ## Step 2: Build Your App Firebase Studio offers two ways to build … For Static Hosting deployment, you'll need to add `output: 'export'` to `next.config.js` — covered in … Click **Publish to GitHub** to create a new repository, or push to an existing one Firebase Studio supports … publishing to GitHub as a private or public repository. … Deploy a Firebase Studio App to DeployHQ Static Hosting](https://www.deployhq.com/blog/deploy-firebase-studio-app-to-deployhq-static-hosting

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/build-errors/yarn-4

In order to be able to use [Yarn 4](https://yarnpkg.com/blog/release/4.0) to build your node projects … , you will need to add the following commands to your build pipeline: ```bash source /opt/nvm/nvm.sh … Manager) 0.40.3 pre-installed, so you can directly source it from `/opt/nvm/nvm.sh` without needing to … - **Stronger Security:** It includes features like "Hardened Mode" to protect against supply chain … - **Modernizing Yarn:** Requires Node.js 18+ to leverage newer javaScript features.

https://www.deployhq.com/support/deployments/ai-deployment-overviews

DeployHQ now offers the ability to generate AI-powered overviews for your deployments, streamlining communication … If you're on a qualifying plan, you can click the **magic wand icon** to automatically generate this … A few things worth knowing: - Instructions are limited to 1000 characters. … - They apply only to the project you set them on. … DeployHQ also uses AI to generate summaries for archived deployments.

https://www.deployhq.com/guides/express

This guide will show you how to automate deployments of your Node.js Express project using DeployHQ. … - A Node.js Express project **DeployHQ Setup** **Create a Project:** Sign up and log in to … Go to **Projects** > **New Project**. Follow the wizard to connect your project repository. … **Server Configuration:** Go to **Servers** > **New Server**. … Set the **Environment** to `production` and enable **Automatically deploy**.

https://www.deployhq.com/support/build-errors/input-required-build-command

a build pipeline, you may come across an issue where input is required, but this isn't possible due to … If you're seeing a `yes|no`, or perhaps a prompt to enter a password, this will require you to either … abort the deployment, or, wait for the build timeout of 30 minutes to complete. … You will then need to check and ensure that your build commands can be run without any human interaction … In the case of authentication requirements, you might need to create a file such as `auth.json` with

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**