0
I always got it for everything related to servers and stuff. I’m running an application that uses the famous nodejs, and my hosting doesn’t support it. So, just for "online" testing I wanted to make my application "localized locally", have online access with an online subdomain, my computer being the server of everything.
I read a few things about changing the file "hosts" (I use Windows) but I did not get much success.
Some soul can help me here?
3
First, DNS (which you call "online subdomain") should have an entry pointing to your IP.
Second, by uploading an application written in nodejs, it is already in theory exposed to the internet. What would be necessary to do is a port re-counting, which can be done by a software called reverse proxy, like the Nginx, for example, and port release in Firewall.
Third, what the archive hosts does is simulate that DNS entry only on your machine. It does not replicate the DNS to the internet. Who does this is the DNS authority that owns your domain.
Fourth, interesting in its place would be to deploy the application on a machine other than yours. Here has a list of servers that support Node.js.
2
If you really want to see your application on your online machine on some domain, have you tried DDNS? noip for example? I have already made my machine accessible online via noip + settings subdomain on my router. My router uses DD-WRT and has functionality for automatic update of my ip in noip services, as soon as I connect, the router sends a command with my new ip pro noip and noip configures the domain to point to my machine. It is also possible to find DDNS services that accept personal domain, formerly if I am not mistaken Dnspark offered this and I used. Another thing is that, non enterprise DSL connection, type Speedy, will block access at port 80, 8080 and other common for servers.
Browser other questions tagged node.js windows
You are not signed in. Login or sign up in order to post.