Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
that’s all nice, but I won’t develop application on VPS… how to get app running from localhost to VPS?
@tom.hromnik: Simply follow this article and instead of running <code>sails new project-name</code> just transfer the files to /var/www/project-name then proceed with the article.
How to transfer files: <a href=“https://www.digitalocean.com/community/articles/how-to-use-filezilla-to-transfer-and-manage-files-securely-on-your-vps”>https://www.digitalocean.com/community/articles/how-to-use-filezilla-to-transfer-and-manage-files-securely-on-your-vps</a>
Good article. Just a quick note… GIT is required by Sails. Try run sudo apt-get install git-core before you install Sails. Worked for me on Ubuntu 12.10.
@jan.strelka this is resolved now-- all the git deps are gone. Thanks for sharing the tip! More deployment info here: https://github.com/balderdashy/sails-docs/blob/master/deployment.md
Chapter Starting up the Sails.js server On the 1st start up of the Sails.js server I had a Grunt error :
root# sails lift
error:
------------------------------------------------------------------------
grunt-cli: The grunt command line interface. (v0.1.13)
Fatal error: Unable to find local grunt
.....
Possible causes were indicated like this one:
*-> Are "grunt" and related grunt task modules installed locally? Run `npm install` if you're not sure.
So (still in your project folder) run the npm install command and all Sails missing modules will install… and fortunately it resolves this nasty Grunt error.
root# npm install
Chapter Setting the Server to Production Mode “When you are ready to deploy an app to production, moving it from port 1337 to 80, Sails.js allows you to do this easily. 1. Open up config/application.js. …”
It looks like that in the last version of Sails.js (0.10.4) this file does not exist anymore. We should look instead in config/env/production.js
Chapter Setting the Server to Production Mode
“3. If there are multiple apps on the server and if you are running NGINX: You will need to modify the server block config to proxy the port that your Sails.js app is being run on by adding:…”
You should precise: " You need NGINX or APACHE to manage multiple apps. So if you prefer NGINX first install it and read about those 2 articles :
A/ How To Host Multiple Node.js Applications On a Single VPS with nginx, forever, and crontab
B/ How To Set Up Nginx Server Blocks (Virtual Hosts) on Ubuntu 14.04 LTS "
Assuming no nginx or Apache (will run on default port 1337 or some other port), what’s the typical/common path for a Sails app? Does it matter?
I get after typing this in the console:
sudo npm install sails -g
this error log message: sails@0.11.0 preinstall /usr/local/lib/node_modules/sails node ./lib/preinstall_npmcheck.js
Sails.js Installation: Checking npm-version successful npm WARN deprecated grunt-lib-contrib@0.7.1: DEPRECATED. See readme: https://github.com/gruntjs/grunt-lib-contrib
ws@0.5.0 install /usr/local/lib/node_modules/sails/node_modules/sails-hook-sockets/node_modules/socket.io/node_modules/engine.io/node_modules/ws (node-gyp rebuild 2> builderror.log) || (exit 0)
and sails is not installed. Can someone help me?
Thank you for this nice article! I got a question related to the section Setting the Server to Production Mode 3.: If I choose to run Sails on a proxy_pass on port 1337 what would be the recommended way to limit access to my Sails API to localhost? I’d like to run multiple apps on my droplet and use Sails as my API that should only be accessible by the apps in my droplet. – Thanks in advance!