<--
-->

Dynamic Content / Server Executable Rules

  1. The most important rule to follow is to write code that is not intended to "hack", "deface" or otherwise do harm to another person's computer or content. The university's computer use policy is quite clear on all of this.
  2. Do your best to make sure the code you write is secure, or not hackable.
  3. Also very important, follow a schedule to check for updates on any third-party software you install. If you install software provided through your cPanel Scripts Library you can be automatically notified, via email, when updates are available. The web server maintainers are already providing software for you via the cPanel Scripts Library, such as Coppermine (a photo gallery), phpBB or YaBB, some Wikis and some CMS software. It may not be the software of your choice, but the maintainers have chosen it for reasons that are beyond your control, specifically the way it fits into the storage, network, and web service infrastructure. If there is an application you would like to run, please let them know and they will try to find a way to make it available through your cPanel Scripts Library. If this is not possible, they will let you know so that you are aware you can install it yourself. You may contact them via email at studentorg@mtu.edu.
  4. All programs, perl, php, etc. must reside in your "cgi-bin" directory. See the "Where do I put my web site on the server" section of the FAQ.
  5. Technically, server side includes (SSI) are dynamic content. SSI is the exception to rule 4. SSI can be in any directory, not just "exe", and is available by default.