Issues with deploying to baremetal
The Wasp application is deployed, but all requests (including static assets) are being caught by the catch-all route, resulting in a "{"message":"Catch-all route"}" response.
- Apache is configured as a reverse proxy.
- Node.js server (Wasp backend) is running on port 5555.
- Static files are present in the correct build directory.
We've tried updating the Apache configuration to serve static files and proxy only API requests. I can verify that the Node.js server is responding correctly to API requests.
The application works correctly in development mode with wasp start.
Static assets are not being served properly in production; loading for instance http://<mysite>/index.html or http://<mysite>/login is being routed to the catch-all route, seemingly intercepting all requests.
- Apache is configured as a reverse proxy.
- Node.js server (Wasp backend) is running on port 5555.
- Static files are present in the correct build directory.
We've tried updating the Apache configuration to serve static files and proxy only API requests. I can verify that the Node.js server is responding correctly to API requests.
The application works correctly in development mode with wasp start.
Static assets are not being served properly in production; loading for instance http://<mysite>/index.html or http://<mysite>/login is being routed to the catch-all route, seemingly intercepting all requests.
