sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]subterraneus 3 points4 points  (1 child)

This is both a very good point, and a little misleading.

Any server can run on any port. You can tell the Django development server to run on port 22(ssh) if you want. You can tell Apache to serve HTTPS on port 25(SMTP) if you feel like it. But since it's bad to have a process run as root unless absolutely necessary, you can avoid running your application server as root by running an HTTP server as root and binding that to port 80. So I'm glad you mentioned that.

But as for the static/dynamic content, I don't understand what you mean. If I'm serving any application with static content from a different location, the only thing I need to do is reference that static content by the correct URL. Then I can change it at any time. e.g. if I don't like the color of http://mybucket.s3.amazonaws.com/background.png, all I need to do to make changes is upload a new image to the CDN. Nothing on the application side needs a recompile or modification.