You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Ensure the `VITE_DEPLOYSTACK_APP_URL` points to where your backend service is accessible. If running both containers on the same Docker host, `http://localhost:3000` (or the host's IP/hostname if `localhost` doesn't resolve correctly from within the frontend container's network to the backend's exposed port) should work.
138
+
- Ensure the `VITE_DEPLOYSTACK_BACKEND_URL` points to where your backend service is accessible. If running both containers on the same Docker host, `http://localhost:3000` (or the host's IP/hostname if `localhost` doesn't resolve correctly from within the frontend container's network to the backend's exposed port) should work.
138
139
- The `$(pwd)`in the backend command assumes you are in the root of the `deploystack` project directory. Adjust the path to `services/backend/persistent_data`if running from elsewhere, or use an absolute path or a Docker named volume.
139
140
141
+
#### Production Deployment
142
+
143
+
For production deployments on a VPS or remote server, update the environment variables to use your server's IP address:
0 commit comments