Skip to main content

​
Deploying PipesHub on Azure

PipesHub installs the same way on Azure as anywhere else. This page covers the parts that are specific to Azure; the rest is in the Deployment Overview.
The Google Cloud guide is a complete worked example, including reverse proxy configuration and backup and restore procedures. Those sections are not GCP-specific and apply here too.

​
1. Create the machine

Create a Virtual Machine running Ubuntu 22.04 LTS or later. A Standard_D4s_v3 (4 vCPU, 16 GB) is a reasonable starting point for the full deployment. Attach at least 50 GB of premium SSD storage. Sizing. 16 GB RAM or more for the full deployment, and 50 GB or more of disk. The installer checks both and warns you if the machine is short.

​
2. Open the ports

In the VM’s Network security group, add inbound rules allowing 80 and 443 from anywhere, and 22 from your own address only. Do not expose the database ports. PipesHub reaches them over the internal Docker network, and nothing outside the host needs them.

​
3. Install Docker

Follow Docker’s install guide for your Linux distribution, then add your user to the docker group so the installer can reach the daemon without sudo:

​
4. Install PipesHub

When the installer asks for the Public HTTPS URL, enter the domain people will use. This is written to .env as FRONTEND_PUBLIC_URL and is what OAuth callbacks and email invitations are built from.

​
5. Put HTTPS in front of it

Browsers block features PipesHub needs when the page is served over plain HTTP from anything other than localhost. The usual symptom is a white screen after a deployment that otherwise looks healthy.
Two common choices on Azure:
  • Application Gateway with a certificate from Azure Key Vault, forwarding to the VM on port 3000.
  • Nginx or Caddy on the VM, with a Let’s Encrypt certificate. Simpler, and no gateway cost.
Whichever you choose, terminate TLS there and forward to PipesHub on port 3000.

​
6. Check it is running

Then open your domain in a browser and complete the onboarding.

​
Day-two operations

Run these from ~/pipeshub:
For backup and restore, follow the procedures in the GCP guide — they operate on Docker volumes and are not specific to any cloud.