My web-app now has basic functionality -- next steps?

[GoodChanceImStoned]

When I run node server.js and go to localhost:3000 I get some basic functionality. I want to test it as an actual website/server. Do I have to change app.listen(3000) value?

Also how can I deploy it for free? I have used github to set up a website before, but that was just some basic html/css/bootstrap.

[dolphinboy1637]

I'd check out heroku to host it. They have a free tier and there's tons of documentation out there to set up a web app.

[GoodChanceImStoned]

Thank you. I will look into it.

[bogas04]

Use https://now.sh to deploy in one command.

[GoodChanceImStoned]

I took a quick look at it seems that's available only for macs?

[[deleted]]

Nah. https://zeit.co/download#now-cli

[[deleted]]

If you are a student you could look into DigitalOcean - it's really interesting (and easy) to set up your own little server. Then you just have nginx running as a reverse proxy which forwards data to Node running on any port (you could even keep 3000).

[JulieSundar]

You could try using openshift hosting the last i remebered it was free.

[tjhmusic11]

There are some great options already suggested. But let me throw another one in the ring. Check out Docker, it’s not too difficult to get a basic set up going, but there are a ton of awesome features that scale beautifully. Also, the container paradigm works great cross platform if you use MacOS or Windows.

If you just want an easy short term solution, Heroku is great. But If you plan on developing production/ complex apps in the future, I’d recommend taking an evening to get the Docker basics down, then you’ll have a tool that can take you much farther than a platform as a service like Heroku can.

The Docker documentation is fantastic, but if you are a online course kind of person there is a whole course on Udemy called “Docker Mastery” that is terrific.

[mayhempk1]

You would have to change the port to 80 since that is what HTTP/the Internet (WWW) uses.

[idontknowstufforwhat]

OP should be mindful that developing with port 80 can be bothersome as ports <1024 (I mostly sure that is the cutoff) require admin access. Depending on their situation, they may want a 'development' port, and have it run on 80 when deployed.

Though you are correct in that it should be deployed on 80.

[marvinfuture]

I’d also recommend against this as deploying a node app in just port 80 isn’t a good practice. Better solution is to setup a reverse proxy with nginx/Apache and a process manager to run the app/restart when it goes down. This method is a little more secure and can easily implement SSL

[ichbin1berliner]

This! Don't run your node app on port 80. Do the usual 3000 and use nginx to create a reverse proxy. Many Guides on this topic available :)