4 ms·
give you a server that can run 90% of what a user needs Are you saying that you just keep adding things to the server until you've covered that mythical user?
by corresation 13y ago
give you a server that can run 90% of what a user needs
Are you saying that you just keep adding things to the server until you've covered that mythical user?
That sounds like an absolute disaster from a security, maintenance, and resource usage perspective.
I don't see what problem this solves. Start an EC2 instance (takes seconds), configure it as you want it (which to me includes a hardened, specific set of software with very specific routing rules where nginx sits in front of node, etc), and then save an AMI from your specific mix of technology.
Trivial, and perfectly suited to the user's needs. I can then spin up any number of perfectly suited instances.
- Karunamon 13y ago>That sounds like an absolute disaster from a security, maintenance, and resource usage perspective. Installed and available are a huge sight different from running and exploitable, though. I can have a completely unpatched Apache from 5 years ago, it's invulnerable to foes up to and including the NSA unless the app is running and listening on a port :) Would be trickier, but not impossible for more system-level apps like Cpanel/Virtualmin.
- mey 13y agoWhat makes you assume an apache httpd install is secure simply because it is not running an "app"? http://httpd.apache.org/security_report.html http://httpd.apache.org/security_report.html
- jlgaddis 13y agoI think he meant it's invulnerable if httpd (the "app") isn't running.
- gcr 13y agoIn the context of web applications, would it make sense to stop using the word "app" to refer to software/daemons available in the distribution repositories, and instead only use "app" to mean the products and services built on the former?
- Karunamon 13y agoapp == application == executable computer code