https://www.deployhq.com/support/notifications/browser

in your DeployHQ account you can set up browser notifications for a running deployment in DeployHQ, to … when the deployment starts, then when it has completed. ## Setting up browser notifications To … enable browser notifications, head to the **Settings** tab at the top of the screen, then to **Profile … In order to receive a notification, you'll need to have the deployment open in any tab in your browser

https://www.deployhq.com/support/integrations

. ## Managing Integration Order You can reorder your integrations to control the sequence in which … To reorder integrations: 1. Navigate to your project's integrations page 2. … Use the drag handle (reorder icon) next to each integration 3. … Drag integrations up or down to change their execution order 4. … to bottom. ## Available Integrations Click on a service below to find out more about how to set

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

user authentication and a database to store tasks … — lives in [How to Deploy a Lovable Frontend to DeployHQ Static Hosting](https://www.deployhq.com/blog … /deploy-lovable-frontend-to-deployhq-static-hosting). … Supabase continues to handle auth, database, storage, and Edge Functions. The pipeline: 1. … For a standard Lovable project, set the build command to `npm ci && npm run build`.

https://www.deployhq.com/support/managing-your-account/personal-profile/profile

If you head to the **Settings** tab at the top of the DeployHQ interface, then to **Profile** on the … 165} You can update your **First Name** and **Last Name** directly from the page, then find a link to … will then show deployment log information and other timestamps in DeployHQ appropriately according to

https://www.deployhq.com/cheatsheets/cron

Crontabs are the per-user files that tell it what to run; every Linux server with scheduled tasks (backups … # every minute */5 * * * * cmd # every 5 minutes 0 * * * * cmd # top … Setting `PATH` near the top of the crontab catches the #1 production failure ("works in my shell, not … redirection patterns ```cron * * * * * cmd # stdout/stderr mailed to … per-application schedules installed by a package manager or a deploy hook — one file per app, easy to

https://www.deployhq.com/support/faq/how-to-change-billing-frequency

Navigate to **Settings** in the top navigation bar 3. … Click the **Switch to Yearly** button on your current plan card 7. … Navigate to **Settings** in the top navigation bar 3. Select **Subscription Plans** 4. … Click the **Switch to Monthly** button 7. … monthly, you keep access for the full year already paid Feel free to reach out to our <a href="https

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

to get started. … connect to your RackNerd VPS. … enter the path to the theme. … , because there is no previously deployed commit to compare to. … how you ship to RackNerd?

https://www.deployhq.com/support/api/beta-enrollment-api

The Beta Enrollment API allows you to enable the managed-resources beta (Managed VPS and Static Hosting … This is used by the DeployHQ CLI (`dhq launch`) to enable the beta before provisioning managed infrastructure … **Tip**: You can explore and test this endpoint interactively using our [OpenAPI documentation](https … ---|------------------| | Account administrator | Enrolls and returns success | Returns success (no-op … ) | | Non-admin member | Returns 403 with `admin_required` | Returns success (no-op) | ## Enroll in

https://www.deployhq.com/cheatsheets/postgresql

It's the tool you drop into to check a schema before a migration, run a query file as part of a deploy … This sheet covers the meta-commands and SQL you actually use day to day, plus the deployment-specific … TABLES IN SCHEMA public TO app_runtime; GRANT SELECT ON ALL TABLES IN SCHEMA public TO readonly; GRANT … readonly TO analytics_user; -- grant a group role to a user -- Make privileges … apply to FUTURE tables too (the common gotcha): ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT

https://www.deployhq.com/support/build-errors/Javascript-heap-out-of-memory

In order to solve that, please declare the following environment variable on top: export NODE_OPTIONS … that is a hard limit and cannot be increased I'm afraid, however, you can certainly move the process to