Code

The repo, what Vercel builds, the roots, and Import a zip.

Settings › Code is the repository and what gets built from it: the repo's row, what lives where, and Import a zip.

Repository

The row names the repo, owner/name, and its branch, in the FlexOS organisation on GitHub. A new project has it from the first minute; a project that somehow has none shows No repo yet, and the owner connects it there.

What lives where

• Website folder: the folder Vercel builds. Blank means the top of the repo. An imported zip sets it to the folder the website was found in.
• Mobile app folder: where a phone app lives, app/ by default. It is kept off the website. Changing the folder moves no files.

Import a zip

Code you already have comes in here (or on the new-project page). Before anything is uploaded, the page reads the zip and shows What goes where:

• Website folder: the folder with the website in it, put online. No website found means the code goes into the repo and nothing goes online from it.
• Keys to the Vault: a .env is never committed. Its keys go into the Vault under the names they had. A keystore, a service account or another key file is kept whole in the Vault, as a file.
• Left out: installed packages, git history, build output, and the resource forks a Mac adds. A .env.example is meant to be committed, and is.

Your files go into the repo in one commit, as they are. Nothing reads or rewrites the code on the way in; Flexi meets it in the repo like any other file. The import does not touch .flexos/.

A website zip with a folder named app/ (Nuxt and Next have one) is refused while a phone app lives there. Move the app's folder first, in this panel.

Where next

• Bring your code: a Lovable export, an old site, any codebase.
• The Repo: what the repository holds.

Start free · Rebuild your website · Docs · FAQ