-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
local mode does not come up when HOST
is not resolvable
#18
Comments
Cool. Seems like this might be fixed in Remix v2, which I am in the process of upgrading to in oxidecomputer/rfd-site-old#238. v1.19v2It might always use |
I checked and v2 does not fix this, it does the same thing.
What do you think it should be doing instead? Do you think local dev should always use - "dev": "remix dev",
+ "dev": "HOST=localhost remix dev",
|
That seems fine. I don't know enough about Remix to have much opinion. A lot of stuff assumes that a system's hostname is resolvable in DNS, but that's generally not a great assumption. Usually if I want something to listen on anything other than I would also be happy with an error message that said that it failed to come up because of this (and ideally where it got the hostname from) and then exiting instead of just hanging. The real reason this was annoying was that I spent time trying to guess if it came up anyway (I noticed it did open port 3001 and tried that) and also guessing where it got Thanks for looking at this! |
On my system,
HOST=zathras
(in the environment). Butzathras
is not resolvable in DNS. If I run this, it reports this error and then sits there, not having started listening on port 3000:I was confused about whether this problem was fatal or not. It seems like it basically is but the program doesn't exit. I worked around it by setting HOST=zathras.local.
The text was updated successfully, but these errors were encountered: