### Source Peer feedback, collected in #167. Quotes (translated): the Vite proxy is used well to avoid CORS problems, but the frontend code that shows the images does not use the proxy and can be why the images did not show; add environment variables to the configuration so the frontend can use the backend on the VM when working with only the frontend locally. ### Already done on `dev` (#188 and related) - The image address goes through the app's base path (`src/lib/imageUrl.ts`), and Vite proxies `/project2/images` as well as `/project2/graphql`. - `VITE_API_URL` sets the GraphQL address and is mentioned in `docs/VM_SETUP.md`. - The backend port is 4000 everywhere. ### What is left - [ ] The proxy target in `vite.config.ts` is fixed to `http://localhost:4000`. With `VITE_API_URL` set to the VM, the API calls go to the VM but the images still go to the local backend. Let one environment variable (for example `VITE_BACKEND_URL`) set the target of both proxies, with `http://localhost:4000` as the default. - [ ] Add a `.env.example` in the repository root for the frontend variables (`VITE_API_URL` or the new one, `VITE_DEV_LOGIN`). Today there is only `backend/.env.example`. - [ ] Write the steps for frontend-only work against the VM in the README "Getting started", and check that the login works against the VM backend. ### Done when - [ ] Someone who only runs the frontend can use the backend of the VM, and the images show. _Comment made with Claude Code in discussion with Ronja_