Do Your Really, Really Need to Run Your Own Webserver?
  Some Practical Alternatives and Suggestions
Anne Salemme MIT IT Partners Conference October 24, 2002

Introduction

"No Cost" Option:
 Use web.mit.edu

"Some Cost" Option:
 Run a content-less webserver

"Some Cost" Option:
 Let W91 do it

"Last Resort" Option:
 Do-it-yourself

Webserver management essentials

Useful links

Example: webmail.mit.edu

About me

Webserver management essentials

Whether you run your own webserver, use one that is run by someone else, or hire someone to run yours, here are some things that need to be done on an ongoing basis:

  • Keep the system hardware and operating system up to date
  • Watch the system logs for indication of problems
  • Keep up with security advisories and apply fixes
  • Keep the webserver and its underlying software up to date, monitor logs, keep up with security advisories, and apply fixes
  • Make sure updates don't break website
  • Make sure automatic startup and shutdown of webserver and its underlying software work properly
  • Continually check such things as: disk full, certificate expired, unusual activity
  • Generate a daily report to show that the website is working properly
  • Monitor performance to plan for future capacity issues
  • Troubleshoot problems in a non-invasive way; it is necessary to have a good test environment for any production website
  • Have backup and contingency plans working and tested
  • Consider using a persistent url which you publish, such as http://mit.edu/mylab . That will provide a link to your actual website, which you can easily change. (If you publish http://mylab.mit.edu, and you have to change it, people and old bookmarks may have a hard time finding the new url.)

Updated October 23, 2002. Copyright © 2002 Massachusetts Institute of Technology
Written by salemme@mit.edu