Deploying through GitHub

Navigate to Services

1. From the Aquanode Console, go to Workloads → Services or at GitHub Deployment.
2. Select the GitHub Repo option.

This opens the GitHub Deployment screen where you can connect your repository.

Configure Source Control

• Repository URL → Enter the HTTPS link to your public or private GitHub repository, e.g. https://github.com/username/repository.
• Branch → Specify which branch should be built (default: main).
• Private Repository → If deploying from a private repo, you will need to provide a valid GitHub access token with repo scope.

This tells Aquanode which codebase to fetch and build.

Build Settings

Define how your application should be built and started:

• Language → Currently supported: Node and Python.
• Framework (Optional) → Select from supported frameworks (if applicable).
• Install Command → Command to install dependencies (e.g., npm install, pip install -r requirements.txt).
• Run Command → Command to start your app (e.g., npm start, python app.py).
• Port → Port your app listens on (default: 3000).
• Output Directory → The build output folder (e.g., dist, build).

Example (Node.js app):

• Install Command → npm install
• Run Command → npm start
• Output Directory → dist
• Port → 3000

Resource Settings

Select the resources your deployment should use:

• CPU Allocation → Number of cores (e.g., 1).
• Memory Allocation → RAM allocated (e.g., 16 GB).
• Storage Allocation → Persistent storage (e.g., 40 GB).

Optional:

• GPU Configuration → If your app requires GPU acceleration, select from available GPUs (H100, A100, B200, RTX series).
• Use filters to refine by provider (Voltage Park, DataCrunch, Akash Network, Hyperstack, Vast.ai, Vultr, Massed Compute, Cudo Compute, Hot Aisle) or region.

If GPU is not selected, the deployment runs on CPU-only nodes.

Deploy

1. Review your configuration.
2. Click Deploy on GitHub.
3. Aquanode will:
   • Clone your repository
   • Run the install and build commands
   • Launch your application as a service

Deployments typically take a few minutes to become active.

Once live, you can view your service in the Active Services tab.