Moving from Lovable, Bolt, v0 or Replit.
The builder writes the code. Yawl runs it on your server.
Connect to GitHub
In the builder, so the code lives in a repository.
Read the repository
New service, Import an app. Paste the URL and read the checklist.
Apply and deploy
Later changes in the builder reach GitHub and deploy.
What becomes what
| Area | What | In Yawl |
|---|---|---|
| Builders | Lovable | Found by lovable-tagger in package.json. A Vite site, built with Node and served as files. |
| Bolt | Found by a .bolt folder. A Vite site, or a Next.js app with next start. | |
| v0 | Found by the package name my-v0-project. A Next.js app. | |
| Replit | Found by a .replit file. Its [deployment] run command, after its build. | |
| Keys | VITE_* NEXT_PUBLIC_* | Build-time, written into the page. Anyone can read them: never a secret. |
A committed .env | Read by the build. Yawl does not ask for those keys. | |
| Replit's own keys | Not asked for. Yawl warns; move that data to a Yawl Postgres. | |
| Supabase | The project | Stays on Supabase, with its functions. |
| Sign-in | Add the new address in Supabase, Authentication, URL Configuration. | |
| Not yet | ZIP uploads | Push the code to GitHub first. |
| Supabase data | Not moved into a Yawl Postgres. | |
| Expo apps | Refused at Read repository. |