4 ms·
Good post! Ad 2.: Ok, that's right but rather a general prerequisite, so I would remove it from the list. Ad 3.: Yes, this is recommended. 4. and 5. are good
by tferris 14y ago
Good post!
Ad 2.: Ok, that's right but rather a general prerequisite, so I would remove it from the list.
Ad 3.: Yes, this is recommended.
4. and 5. are good steps but optional and should be done in later stages otherwise it's typical premature optimization
6. Optional you could use hosted solution like MongoHQ
7. Just install and use Git??
8. DDOS defense? There's no standard recipe
> I can see why you would want an automated PaaS to take care of all these things for you.
I agree with you that automated hosting is nice but somehow the bizmodel doesn't seem to appeal. But again, compare this to the Rails world: How many automated hosters do you see there? Not many more.
- rpwilcox 14y ago> 7. Just install and use Git?? I made that point generic for a reason. :) So you git push to your remote, now you (may) have to tell the servers to reload. Along with other things (database migrations if you're using SQL, compiling native code if you have any of that, potentially updating configuration files if your app needs that, updating assets on a CDN/cache etc). Yes, sure, a post-receive hook can be wired to do these things, but you have to know that and do the wiring.
- mmobile 14y agoHow is this post receive hook done ideally with Node and Git?