This page describes the web hosting options provided by the School of Informatics and Computing. This includes provisions for personal homepages as well as project, course, and research group pages. You can create your own homepage using several of the web hosting options described below using the Homepage Management Page. Please contact the systems staff if you need help setting up any of these options. In your request, please include the naming convention and hosting option (see below) that you prefer.
The normal naming conventions/URLs are as follows:
Personal Homepages - See the Homepage Management Page to set up your homepage.
Project/Research Homepages (With SoIC Faculty Sponsorship)
The IU Oncourse Systemprovides homepage support for all IU classes. Oncourse is easy to use and provides features like blogs, chat rooms, email lists, grade management, and more. However, we also provide support for course homepages for instructors to use instead of, or in addition to, Oncourse. Course homepages hosted on the SoIC servers use urls of the form:
For example, for INFO I100 taught in the Fall 2011 semester by an instructor with username janedoe, the url would be
For more information about course homepages and ways you can upload supplemental information about your courses to the SoIC web site please see How do I upload information about classes I'm teaching?.
Multi-Unit Project/Research Homepages (With SoIC Faculty Sponsorship and IU Approval)
Please note that sites within the indiana.edu domain (as opposed to the soic.indiana.edu domain) are reserved for projects that span multiple schools, departments, or organizations on the Bloomington campus. A project that exists completely within the SoIC will normally be created within the soic.indiana.edu domain. To request a domain within indiana.edu, the sponsoring faculty member must write a short justification describing the inter-unit nature of the project.
Multi-Campus Project/Research Homepages (With SoIC Faculty Sponsorship and IU Approval)
Please note that sites within the iu.edu domain (as opposed to the soic.indiana.edu domain) are reserved for projects that span multiple IU campuses. A project that exists completely within the SoIC will normally be created within the soic.indiana.edu domain and projects that span multiple units on the Bloomington campus will normally be created within the indiana.edu domain. To request a domain within iu.edu, the sponsoring faculty member must write a short justification describing the inter-campus nature of the project.
You can use any of the hosting options described below with these URL naming conventions.
Note that soic.indiana.edu is the new domain for the school and is preferred over the legacy cs.indiana.edu and informatics.indiana.edu domains.
A number of hosting options are available at IU and within the school, each with its own advantages. You can create your own homepage using several of the web hosting options described below using the Homepage Management Page. Please contact the systems staff if you want to set things up for a group or project page.
- Webserve - Webserve is the standard Apache/PHP/MySQL web hosting environment at IU and you are encouraged to use it. To help get you started, we've put together a Webserve Quick Start Guide. In addition to Webserve, IU also offers Oncourse, Confluence, Mypage, and the Consolidated Hosting Environment (CHE). The remainder of the offerings in this list are provided by the School of Informatics and Computing for use only by members of the SoIC.
- Pages - Pages is a web hosting platform provided by UITS for hosting professional, research, instructional, and academic content. You will have a url of the form and this service provides a simple html hosting platform.
- Wordpress - Wordpress is a popular content management systems for building web sites. It offers a wide range of features like blogs, themes, forums, customizable user roles, and web-based administration. This options is available for faculty, staff, graduate students, and research/project sites and is a good option for anyone wanting a full-featured content management system. This services is managed by the systems staff but users have full control over the content of their sites.
- HTML Hosting - You are provided with a directory into which you can publish your html. This lets you use any html web site creation package (such as KompoZer, Dreamweaver, or Expression Web) or you can write your own html code. This option does not provide any type of content management system so you will either have to use some other package to do this or you can do it manually. Access to the directory will be via ssh/scp/sftp and most publication packages support publication using this mechanism. This option supports static html hosting only so does not support PHP or CGI.
- CGI/PHP Hosting (Linux) - If you need PHP or general CGI support, then this option may meet your needs. This is similar to the HTML Hosting option but includes support for PHP as well as CGI using the programming language of your choice (perl, python, ruby, etc). While this option provides the most power and highest degree of customization, it is not recommended for anyone without experience working in a Linux environment. In addition to writing your own code, you can also use this option if you need support for 3rd-party PHP or CGI-based applications (such as mediawiki, gallery, geeklog, etc). This options is available for faculty, staff, students, and research/project sites.
- Group-owned Server - If you have your own server where you can run something like apache, you can host your own site, with faculty sponsorship. We can set up the DNS records for you and you can manage the site yourself. This can be done on a system that the SoIC staff is managing or a system you manage yourself.
- Hosted Server - If hosting your site using one of the above services is not practical, it is possible for us to set up a virtual machine that either we can manage for you or you can manage yourself, with faculty sponsorship. Bear in mind that this option typically takes significantly more staff resources than any of the above options, so we will have to negotiate a support model that doesn't put undue burden on the systems staff.