Sails: How to run sails.js application on port 80 with example?

Created on 31 Jan 2014 · 24Comments · Source: balderdashy/sails

I want to run sails.js application ny default to 80 not 1337.

My local url must be like this http://localhost not http:localhost:1337

Source

JigneshPansuriaDeveloper

Most helpful comment

Set the port in config/local.js to 80, or specify env PRODUCTION and add the conditional. If you do this (run on port 80), you must either run sails as root, or forward a port higher than 1024 to port 80 (because ports under 1024 require root privilege).

Here's an example to use with iptables:

--iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
--iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT
--iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080

Update: Please ask this question on stackoverflow! We keep asking you to do that. At some point people will start ignoring you. So post this question on stackoverflow so it can be answered in dept there.

RWOverdijk on 31 Jan 2014

👍4 ❤1 😄1

All 24 comments

Here's an example to use with iptables:

--iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
--iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT
--iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080

RWOverdijk on 31 Jan 2014

👍4 ❤1 😄1

i change like this below in local.js

/**

Local environment settings
*
While you're developing your app, this config file should include
any settings specifically for your development computer (db passwords, etc.)
When you're ready to deploy your app in production, you can use this file
for configuration options on the server where it will be deployed.
*
*
PLEASE NOTE:
This file is included in your .gitignore, so if you're using git
as a version control solution for your Sails app, keep in mind that
this file won't be committed to your repository!
*
Good news is, that means you can specify configuration for your local
machine in this file without inadvertently committing personal information
(like database passwords) to the repo. Plus, this prevents other members
of your team from commiting their local configuration changes on top of yours.
*
*
For more information, check out:
http://sailsjs.org/#documentation
*/

module.exports = {

// The port setting determines which TCP port your app will be deployed on
// Ports are a transport-layer concept designed to allow many different
// networking applications run at the same time on a single computer.
// More about ports: http://en.wikipedia.org/wiki/Port_(computer_networking)
//
// By default, if it's set, Sails uses the PORT environment variable.
// Otherwise it falls back to port 1337.
//
// In production, you'll probably want to change this setting
// to 80 (http://) or 443 (https://) if you have an SSL certificate

port: process.env.PORT || 80,

// The runtime "environment" of your Sails app is either 'development' or 'production'.
//
// In development, your Sails app will go out of its way to help you
// (for instance you will receive more descriptive error and debugging output)
//
// In production, Sails configures itself (and its dependencies) to optimize performance.
// You should always put your app in production mode before you deploy it to a server-
// This helps ensure that your Sails app remains stable, performant, and scalable.
//
// By default, Sails sets its environment using the NODE_ENV environment variable.
// If NODE_ENV is not set, Sails will run in the 'development' environment.

environment: process.env.NODE_ENV || 'PRODUCTION'

};

but still http://localhost not working

it gives blank page

JigneshPansuriaDeveloper on 31 Jan 2014

http://localhost:80 also not working

JigneshPansuriaDeveloper on 31 Jan 2014

Read my previous answer.

RWOverdijk on 31 Jan 2014

http://localhost:8080/ like this working but http://localhost not working

JigneshPansuriaDeveloper on 31 Jan 2014

Read my first answer.

RWOverdijk on 31 Jan 2014

Do u have full source code..

JigneshPansuriaDeveloper on 31 Jan 2014

Just chiming in here as @rRWOverdijk already said it, just didn't give a command .. node can't lift sails on lower level ports without a sudo infront of it.. sudo sails lift