8 ms·

Deploying SailsJS Apps in Seconds

43 points by mikermcneil 12y ago

oneweekwonder 12y ago
Is it just me or are the documentation lacking?
- mikermcneil 12y ago
  What are you seeing in particular?
pjmlp 12y ago
Just discovered yet another JS framework.
bonn1 12y ago
I thought the 'Rails' approach with tons of magic and thick layers of abstraction as one monolithic something does not reflect the Node mindset of being modular. With Express, Koa and other minimal stacks the Node ecosystem is quite happy and maybe thats the key motivation they moved to this stack. Almighty Rails-esque frameworks—or already the word 'framework' is a bit a thing of the past. Small one-purpose libs are the way to go, at least in Node-land or did I miss anything?
- mikermcneil 12y ago
  Legitimate point-- at the same time, conventions help you get stuff done. They way I solved that in Sails is by federating the monolithic framework logic into smaller modules that can be disabled or overridden (see http://sailsjs.org/#!/features http://sailsjs.org/#!/features) Working on going further down this approach w/ machines- effectively a container layer on top of JavaScript functions (https://www.youtube.com/watch?v=72jI0dQx7pw https://www.youtube.com/watch?v=72jI0dQx7pw)
ffumarola 12y ago
Any plans to make this work with Heroku, Amazon, etc?
- mikermcneil 12y ago
  definitely- working on breaking it out to be easily pluggable
- particlebanana 12y ago
  Should be pretty easy to expand this out to work with any PaaS such as Heroku, Modulus, etc. For aws maybe we could work on getting it to deploy to Elastic Beanstalk? Might also be cool to generate a docker image.
- felixrieseberg 12y ago
  It should be pretty easy to look at the approach I took and mimic it for other providers. I write Open Source code for Microsoft, so we made it work with Azure first - but the code should be clean enough for someone else to pick it up and work in other stacks. I should probably also mention that the engine running Azure Websites is open source itself (https://github.com/projectkudu/kudu https://github.com/projectkudu/kudu), so you could just point it to your own engine.
matthewnolandev 12y ago
Very cool!
cramrod 12y ago
This is nuts.
felixrieseberg 12y ago
Hey guys, Felix here - happy to answer any questions!
byeager 12y ago
Big fan of Sails and the team behind it, very cool to see this.
gvilarino 12y ago
Brilliant stuff. Nice going guys.

43 points by mikermcneil 12y ago

oneweekwonder 12y ago

Is it just me or are the documentation lacking?

mikermcneil 12y ago
What are you seeing in particular?

pjmlp 12y ago

Just discovered yet another JS framework.

bonn1 12y ago

I thought the 'Rails' approach with tons of magic and thick layers of abstraction as one monolithic something does not reflect the Node mindset of being modular. With Express, Koa and other minimal stacks the Node ecosystem is quite happy and maybe thats the key motivation they moved to this stack. Almighty Rails-esque frameworks—or already the word 'framework' is a bit a thing of the past. Small one-purpose libs are the way to go, at least in Node-land or did I miss anything?

mikermcneil 12y ago
Legitimate point-- at the same time, conventions help you get stuff done. They way I solved that in Sails is by federating the monolithic framework logic into smaller modules that can be disabled or overridden (see http://sailsjs.org/#!/features http://sailsjs.org/#!/features) Working on going further down this approach w/ machines- effectively a container layer on top of JavaScript functions (https://www.youtube.com/watch?v=72jI0dQx7pw https://www.youtube.com/watch?v=72jI0dQx7pw)

ffumarola 12y ago

Any plans to make this work with Heroku, Amazon, etc?

mikermcneil 12y ago
definitely- working on breaking it out to be easily pluggable
particlebanana 12y ago
Should be pretty easy to expand this out to work with any PaaS such as Heroku, Modulus, etc. For aws maybe we could work on getting it to deploy to Elastic Beanstalk? Might also be cool to generate a docker image.
felixrieseberg 12y ago
It should be pretty easy to look at the approach I took and mimic it for other providers. I write Open Source code for Microsoft, so we made it work with Azure first - but the code should be clean enough for someone else to pick it up and work in other stacks. I should probably also mention that the engine running Azure Websites is open source itself (https://github.com/projectkudu/kudu https://github.com/projectkudu/kudu), so you could just point it to your own engine.

matthewnolandev 12y ago

Very cool!

cramrod 12y ago

This is nuts.

felixrieseberg 12y ago

Hey guys, Felix here - happy to answer any questions!

byeager 12y ago

Big fan of Sails and the team behind it, very cool to see this.

gvilarino 12y ago

Brilliant stuff. Nice going guys.