How to test Starlight™ Hyperlift deployment with a sample repository

Updated on

This guide will walk you through deploying a simple demo application using Starlight™ Hyperlift. 

To help you test the build and deployment process quickly, without needing to prepare a full production application, we’ve created the Hyperlift Test Repository.

Step 1: Access the Test Repository

  1. Visit our public GitHub test repository: Hyperlift Test Repository;

  2. Click “Fork” to add it to your own GitHub account:

Step 2: Review the Dockerfile

The repository comes with a simple Dockerfile as an example, which starts with a base image: FROM python:3-slim:

You can replace this with an image and tag of your choice, e.g., FROM golang:1.25. 

We recommend always specifying the tag so your builds remain consistent and reliable.

Step 3: Connect Repository to Hyperlift

In your Spaceship account, go to the Starlight Hyperlift Manager menu.

Connect your forked GitHub repository by following the steps from this guide.

Step 4: Deploy the App

After the GitHub repo is connected to Starlight Hyperlift, click on the “Build” button inside Hyperlift Manager:


Hyperlift will build your container image automatically, and within a few minutes, your demo app will be live. Once done, you’ll see a corresponding “App is live” notification.

Step 5: Experiment and Learn

After the application has been built and activated, try editing the code in your repo and pushing the changes. Hyperlift will redeploy if automatic build is enabled.

You can also explore the build and application logs in Hyperlift to better understand how the build process works. 

Finally, use this repo as a safe sandbox before moving on to real applications.

Next Steps

This repository is a quick way to test Hyperlift deployments. It’s intentionally simple but demonstrates the core flow of fork > connect > deploy. Once you’re comfortable, you can move on to deploying your own applications.

For this, you will need to create a Dockerfile with the required base image and configurations. The following documentation will be helpful for you:

A valid email is required