Skip to main content
Import a funnel from GitHub when its pages already exist as code. Olympus builds the repository, reports what carries over, and hosts the result as a funnel. Next.js (static export), Vite, Astro, and plain HTML projects work.

​
Import a repository

1

Connect GitHub

Connect GitHub and install the Olympus app on the repository. See GitHub.
2

Choose the source

Open Build > Funnels, then select Import existing funnel. Choose Connect GitHub. If you have not started a funnel yet, Olympus creates one for the import.
3

Pick the repository

In Import code, search for the repository and choose its branch. Set Subdirectory if the site is not at the root of the repository. Select Use this repository. Olympus starts the build.
4

Review the import report

The report lists each section of the build: Pages, Build variables, Replaced server code, Needs you, Forms, and Tracking. Read the report before you add anything.
5

Add the pages

Select Add these pages to bring the built pages into the funnel. Then review them in the funnel editor and publish.

​
Environment variables

Many sites read settings at build time, such as a map key or a public analytics ID. The build needs those values, and Olympus takes them from a .env file that you paste into the import report.

​
Find the values

  • Local project: copy from the .env, .env.local, or .env.production file in the folder you import.
  • Vercel project: open the project’s Environment Variables page and copy the values, or run vercel env pull in the project folder. That command writes a .env.local file.

​
Paste the file

When the report lists a build variable under Needs you, select Paste your .env file. Paste the whole file and select Save values. You can paste a file that contains secrets. Olympus reads it in your browser and sends only the public values to the server. Then it rebuilds the funnel once with all of them. Olympus keeps the values for this funnel, and every later rebuild uses them.

​
Values Olympus keeps

Olympus keeps values whose names start with NEXT_PUBLIC_, PUBLIC_, or VITE_. The build copies these values into the page’s JavaScript, so anyone who opens the page can read them. Only paste values that are safe to publish, such as a map key limited to your domain.

​
Values Olympus leaves out

Olympus leaves out names without one of those prefixes, such as STRIPE_SECRET_KEY or RESEND_API_KEY. These values usually belong to server code, such as a route that calls Stripe or an action that sends email. Olympus does not run server code, and a build would publish the value in the page. The report lists that server code under Replaced server code. Replace it with Olympus forms, calendars, or checkout. Select Fix with Atlas on an item to open Atlas with a prompt that describes the change.
  • GitHub connects your repositories to Olympus.
  • Funnels covers creating, editing, and publishing funnels.