Add support for `yarn rw dev --port 8080`
See original GitHub issueIn order for vercel dev to proxy to rw, it needs to pass a port.
Ideally this could be a --port flag or it could also use a PORT environment variable.
The flag would need to have precedence over the port defined in redwood.toml, otherwise it will never work since create-redwood-app generates a redwood.toml.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Dockerize RedwoodJS - Get Help and Help Others
yarn redwood deploy docker : I don't think this makes sense. The recommendation might be for projects to create their own custom package.json ......
Read more >requires-port | Yarn - Package Manager
Check if a protocol requires a certain port number to be added to an URL. ... To install it simply run the following...
Read more >Content not from webpack is served from /foo - Stack Overflow
The first problem is that you're serving the content from assets/ but you don't have that directory, you have public/assets/ and that's not ......
Read more >docker-compose and webpack-dev-server hot reloads - Medium
Adding a bind mount allows us to propagate changes from the host machine to docker ... ports: - 8080:8080 volumes: - ./app:/bindmount:rw ......
Read more >Dockerize Local Bedrock & Sage Development with Lando
Dockerize Local Bedrock & Sage Development with Lando ... type: node services: ports: - 3000:3000 tooling: yarn: service: theme. Any ideas?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@styfle my bad! 😅 Nice to meet you and thank you for answering my questions!
Here’s a quick fix: #891
This is easier than implementing a new
--portflag and will solve the problem forvercel dev.