Open meenie opened 2 years ago
@jacobparis Could you please help out with this one?
This issue has been automatically marked stale because we haven't received a response from the original author in a while 🙈. This automation helps keep the issue tracker clean from issues that are not actionable. Please reach out if you have more information for us or you think this issue shouldn't be closed! 🙂 If you don't do so within 7 days, this issue will be automatically closed.
Hi, sorry for dropping this for so long
If you use Gitpod from a desktop IDE (VS Code or JetBrains), this works out of the box. Gitpod will expose all the ports directly from localhost and this works just like it does in local dev
If you use gitpod in the browser, you can install the Local Companion app and tunnel the URL to make it work, but there's nothing out of the box https://github.com/gitpod-io/gitpod/issues/3282
Remix only allows you to set the devServerPort
, but if that were extended to allow a devServerPath
, then we could solve this on Remix's end too.
Have you experienced this bug with the latest version of the template?
Yes
Steps to Reproduce
Click the "Gitpod | Ready-to-code" button to create a new pod for this repo. After the repo starts up and it asks you to allow the ports, it will open up the app in a browser tab. Notice that the URL it's trying to use is something like:
wss://3000-remixrun-bluesstack-<token>.ws-us47.gitpod.io:8002/socket
, but it should connect to:wss://8002-remixrun-bluesstack-<token>.ws-us47.gitpod.io/socket
instead.Expected Behavior
LiveReload should function properly while running on Gitpod.
Actual Behavior
It's trying to connect to the wrong Websocket URL which means LiveReload will not work.