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
We have a docker container for our webserver that is very similar to our prod environment which is good for testing and verification. However, it limits some exciting dev features like building the app in the container setup, in-container watch, HMR, or GH dev containers. Let's set up a separate docker-compose file for development. This could have Laravel running in a container on its dev server and Webpack running in a different container on its dev server. Perhaps this could remove the need for a separate maintenance container.
🕵️ Details
Some known challenges:
CORs on API requests is not properly configured
we have a lot of logic that assumes the API is running on the same host as the web server
might need a reverse proxy container to handle routing from the browser
✅ Acceptance Criteria
Separate docker-compose file for development
Laravel serving the API from it's own container
Webpack serving pages from it's own container
Original docker-compose network remains unchanged
The text was updated successfully, but these errors were encountered:
🛠️ Tooling
We have a docker container for our webserver that is very similar to our prod environment which is good for testing and verification. However, it limits some exciting dev features like building the app in the container setup, in-container watch, HMR, or GH dev containers. Let's set up a separate docker-compose file for development. This could have Laravel running in a container on its dev server and Webpack running in a different container on its dev server. Perhaps this could remove the need for a separate maintenance container.
🕵️ Details
Some known challenges:
✅ Acceptance Criteria
The text was updated successfully, but these errors were encountered: