Skip to content
GigadriveDocs

Quickstart

Deploy a project to Gigadrive Network from a GitHub repository and find the URL it is served on.

Deploy an existing GitHub project to Gigadrive Network. Connecting the repository also creates a deployment for every push.

  1. Sign in to the console

    Open console.gigadrive.de. Gigadrive Network is in early access, so a new account joins a waitlist before it can create anything, and the console shows a join form instead of the usual shell. You are emailed when your account is opened up, and access applies the next time you load the console.

    Once you are in: applications live inside an organization, which owns billing, members, and product access, so create one first if you do not have one yet. Organizations explains what an organization covers.

  2. Open the new application dialog

    Select your organization, then New app. The dialog opens on the Import from Git tab.

  3. Connect GitHub

    Choose GitHub, then Connect GitHub Account to link your GitHub identity. Install the Gigadrive GitHub App on the account or organization that owns the repository, and choose on GitHub's screen whether it may read every repository or only the ones you pick. Connect a GitHub repository covers what the App can do and how to change it later. For a GitLab.com project, choose GitLab instead and follow Connect a GitLab project.

  4. Pick the repository

    Select it from the list. The application name is filled in from the repository name, and you can edit it. Under Advanced Settings you can set a root directory for a monorepo and add environment variables that the first build will see.

  5. Deploy

    Deploy creates the application, links the repository, and queues a deployment of the repository's default branch. The console opens the deployment's Logs tab, where the status moves through Queued, Building, and Deploying before it reaches Ready.

  6. Open the URL

    The Overview tab lists every hostname assigned to the deployment. A production deployment is served at <name>.gigadrive.app. Every deployment also keeps a permanent URL of its own, which is what you share when you need a fixed reference to that exact build.

Other ways to deploy

pnpm dlx gigadrive login
pnpm dlx gigadrive deploy

login signs you in through your browser, once per machine. deploy zips the current directory, uploads it, and prints each status change and log line until it reaches Status: Active or the build fails. In a directory it has not seen before it creates and links an application first, named after the directory unless you pass --name. It needs either a gigadrive.yaml or a framework it recognises, and stops with No config file found and no framework detected. when it has neither.

Neither upload route carries a branch, so both land in the Preview environment and are served on the deployment's own URL. Moving <name>.gigadrive.app takes a connected repository and a branch Production matches.

Every push after the first

A push to a branch of the connected repository starts a build for that branch, and each branch keeps its own <name>-git-<branch>.gigadrive.app alias. A push to a branch Production matches replaces what <name>.gigadrive.app serves once the build reaches Ready. Pushing again to a branch whose build is still running cancels the older build.

Where to go next

Project structure

What the build reads: lockfiles, the build script, the root directory.

Frameworks

The defaults each detected framework brings, and what to change.

Configuration

Declare Functions, routes, assets, and buckets in gigadrive.yaml.

The build system

What runs between a commit and a live deployment.