"Hello World" Examples Frameworks Examples React

Wasp Hello World

A full-stack Wasp application — React client, Node.js API, and PostgreSQL — deployed on Zerops. The client ships as static Nginx assets; the API runs on Node.js 24 with Prisma migrations.

Lightweight project core
Single dedicated container with balancers (L3/L7), logger and statistics services
app
Static

Container

1Shared Core

0.25 GBRAM

1 GBDisk (SSD)

 GitHub repo
api:3001
Node.js

Container

1Shared Core

0.5 GBRAM

1 GBDisk (SSD)

 GitHub repo
db:5432,:6432
PostgreSQL

Container

1Shared Core

0.25 GBRAM

1 GBDisk (SSD)

3Shared Cores

1 GBRAM

3 GBDisk (SSD)

$5.10

Per month for
Resources cost
add
FreePer month for
Lightweight pkg.

After deploying one of the environments and getting to know Zerops, you have two paths forward. 1 Clone our GitHub repositories and use the whole recipe as a template, or if you already have an existing application on a similar stack, 2 integrate the recipe setup with your application.

or
Taking ownership of theenvironment

Local environment hosts the production client and API builds plus PostgreSQL in Zerops while the developer runs Wasp locally against the cloud database via VPN.

Clone the template repositories1Create an access token and install zCLI2Start the VPN3Find your service name4Download environment variables5Configure deployment pipeline6Develop and test locally7Push your code changes8Test your staging application
Deploy more environments

Taking ownership of the Local environment

Clone the template repositories

Fork or clone the following to your local machine or GitHub account:

1. Create an access token and install zCLI

Before you start, create an access token and install zCLI so your local machine can work with your Zerops account.

bash
npm i -g @zerops/zcli
  • Log in with your token:
bash
zcli login <personal-access-token>

If you do not use npm, check the zCLI documentation: https://docs.zerops.io/references/cli

Zerops GUI: Creating a Personal Access Token

lightbulb Tip

Save the token in a password manager right away. You will not be able to see it again after leaving the page. You can always create multiple tokens and revoke them independently.

2. Start the VPN

To reach private databases or services from your local machine, open a secure tunnel into the project network.

  • Run:
bash
zcli vpn up
  • Select your project from the list.
  • Keep the VPN connection active while working locally.
  • Use internal hostnames such as db, redis, or api.

lightbulb Tip

If a short hostname like db does not resolve, try db.zerops. For internal HTTP services reached through the VPN, use HTTP rather than HTTPS.

3. Find your service name

Many commands need the exact name of your service. You can find it in the Zerops Dashboard.

  • Open your project in the Zerops Dashboard.
  • In the project overview, find the service you want to manage.
  • Use this exact name whenever a command asks for <service-name>.

Zerops GUI: Locating the Service Name

4. Download environment variables

Instead of copying values manually, export your service configuration into a local .env file.

  • Export only user-defined variables:
bash
zcli project env --service <service-name> --user-only > .env
  • Remove --user-only if you also need system-generated variables.
  • Add --export if you want the output to include the export keyword for shell sourcing.

lightbulb Tip

You can customize the output with the --template flag. The default format is {{.Key}}={{.Value}}.

5. Configure deployment pipeline

Decide how your code should reach the staging environment.

  • In the Zerops Dashboard, go to Service Settings > Pipelines & CI/CD Settings.
  • Connect your repository.
  • Add a trigger so every push to your main branch starts a deployment automatically.
  • If you prefer manual control, you can use zcli push later instead of Git triggers.

6. Develop and test locally

With the VPN active and your .env file ready, run your application locally while it connects to Zerops-hosted services.

Example PostgreSQL connection:

bash
psql -h db -U user -d database

Example internal API check:

bash
curl http://api:3000/health

7. Push your code changes

When local tests pass, deploy your changes to the staging environment.

If you configured Git triggers:

bash
git add .
git commit -m "feat: implement new feature"
git push

If you prefer pushing directly from your machine:

bash
zcli push <service-name>

8. Test your staging application

Verify the deployment before moving toward production.

  • Open your application through the provided Zerops subdomain.
  • Check runtime logs in the Zerops Dashboard under Service Settings > Runtime Logs.
  • Confirm the app starts correctly and there are no deployment or runtime errors.
Have an app already? Integrate Zerops into it

These services were wired into Zerops with per-service integration guides. Open the Integrate flow to follow the same steps for your own application.

Deploy more environments

Deploy environments for the rest of the development lifecycle

One environment rarely tells the full story — deploy environments for other stages of development to see how they work on Zerops.

Related platform & services docs