communication between vite + react & nestjs internally

Question

Hi, I'm struggling to solve topic problem and have some questions.
I've set up backend and frontend with mentioned technologies. Both of them deployed and frontend is returning what i want but there is a problem in connection between those services and I don't know how to configure that.
My react app is trying to reach backend through proxy (like in development) but it really shouldn't, it should call my internal backend address.
Here is my `vite.config.ts`
```ts
const backendPath = process.env.VITE_MODE === 'development' ? 'http://localhost:8080' : process.env.VITE_API_URL;
const port = process.env.VITE_PORT ? parseInt(process.env.VITE_PORT) : 4173;
const host = process.env.VITE_HOST as string;

export default defineConfig({
  server: {
    port: port,
    proxy: {
      '/api': {
        target: backendPath,
        changeOrigin: true,
        rewrite: path => path.replace(/^\/api/, '')
      }
    }
  },
  preview: {
    port: port,
    allowedHosts: [host]
  },
  plugins: [tsconfigPaths(), TanStackRouterVite({ autoCodeSplitting: true }), viteReact()]
});
```
And `axios` config (it should use /api proxy only in development mode)
```ts
const apiURL = import.meta.env.VITE_API_URL;

export const axiosClient = axios.create({
  baseURL: apiURL,
  headers: {
    'Content-Type': 'application/json',
    pragma: 'no-cache',
    'cache-control': 'no-cache'
  },
  paramsSerializer: {
    indexes: null
  }
});
```

I have configured frontend service to use valid port (in this case it's 3000) and also configured starting command as `vite preview --host`

alexwebgr · Accepted Answer

Hi there,first i would like to understand your architectureyou are using vite and react in the frontend and nestjs on the backendyour backend is available under /apiyou have some env variablesVITE_MODEVITE_API_URLVITE_PORTVITE_HOSTit works fine on your local machine but not on railwayare those env variables defined in the railway service that hosts your code?Why are you calling them VITE_ if they are pointing to the backend servicei think a screenshot of your current architecture would really help  make sure to NOT include any private or confidential info like API keys