Hi, great work on this project!
I was trying to deploy this project to Railway, and I'm running into some issues when running bun run build:
bun run build
$ next build
▲ Next.js 16.1.6 (Turbopack)
⚠ The "middleware" file convention is deprecated. Please use "proxy" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy
Creating an optimized production build ...
✓ Compiled successfully in 2.5s
Running TypeScript ...
Collecting page data using 47 workers ...
Generating static pages using 47 workers (0/9) ...
Generating static pages using 47 workers (2/9)
Generating static pages using 47 workers (4/9)
Error occurred prerendering page "/login". Read more: https://nextjs.org/docs/messages/prerender-error
Error: @supabase/ssr: Your project's URL and API key are required to create a Supabase client!
Check your Supabase project's API settings to find these values
https://supabase.com/dashboard/project/_/settings/api
at <unknown> (https://supabase.com/dashboard/project/_/settings/api)
at <unknown> (.next/server/chunks/ssr/_185ab4e6._.js:55:63)
at cs (.next/server/chunks/ssr/_185ab4e6._.js:59:4544)
at f (.next/server/chunks/ssr/app_login_page_tsx_ccc0019b._.js:1:542) {
digest: '535596981'
}
Export encountered an error on /login/page: /login, exiting the build.
⨯ Next.js build worker exited with code: 1 and signal: null
error: script "build" exited with code 1
It seems like the Next.js build relies on Supabase API keys to be set up. It seems like this only affects the login page, but I feel like that shouldn't be necessary when self-hosting.
Might be too early to make these considerations for self-hosting, but I was really interested in using this in my app and I don't want to burden your deployed version
Hi, great work on this project!
I was trying to deploy this project to Railway, and I'm running into some issues when running
bun run build:It seems like the Next.js build relies on Supabase API keys to be set up. It seems like this only affects the login page, but I feel like that shouldn't be necessary when self-hosting.
Might be too early to make these considerations for self-hosting, but I was really interested in using this in my app and I don't want to burden your deployed version