Files
bracket/docs/content/running-bracket/faq.mdx
Erik Vroon 583eb4e963 Migrate Next.js to Vite (#1397)
Vite is much simpler to use than Next.js and we don't need any of the
features Next has that Vite doesn't have.

Benefits of moving to Vite are:
- Much better performance in dev and prod environments
- Much better build times
- Actual support for static exports, no vendor lock-in of having to use
Vercel
- Support for runtime environment variables/loading config from `.env`
files
- No annoying backwards-incompatible changes on major releases of Next
- Better i18n support without having to define getServerSideProps on
every page
- Better bundle optimization
- No opt-out Vercel telemetry 

Also replaces yarn by pnpm and upgrades mantine to 8.3
2025-11-12 11:18:06 +01:00

18 lines
571 B
Plaintext

---
title: FAQ
---
# FAQ
## I ran Bracket with the default `docker-compose.yml` but I can't connect to the backend?
This is likely because you are trying to access Bracket on a different address than
`http://localhost:3000` in the browser. In that case, two things need to be changed:
- Change `VITE_API_BASE_URL` to the address of the backend, e.g `https://api.example.org`.
- You will also need to update `CORS_ORIGINS` to the address of the frontend, e.g.
`https://app.example.org`.
Please consult [configuration docs](configuration.mdx) for more information.