*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
By default, your new Cornell Stack instance(s) will come with a permit of the form cit.lamp.<*instance name>.* or an Active Directory "permit" group in the form on cit-lamp*-<instance name>*, unless you provide one. The initial membership of this permit will be the primary contact, the secondary contact, and all additional authorized users listed on the signup form. Additionally, the primary and secondary contacts for the instance will also have the update privilege to update membership to the permit via the ActiveRoles Server interface at https://admgmt.activedirectory.cornell.edu/permits/default.aspx (Internet Explorer required). Instructions for using the interface can be found at http://www.cit.cornell.edu/services/active_directory/howto/videos/manage_legacy_permits/index.cfm
DAV Access Control
Access to the key generation page of DAVPortal is restricted to valid-user. Access to the DAV share itself by default is restricted to the permit created with your LAMP instance. This is to allow the use of the require netid directive in combination with DAVPortal. Though anyone with a NetID can receive a DAVPortal key for your instance, by default, only those in the permit will be able to actually access the share. The rest of the configuration is up to you - please feel free to adjust it to your needs through the use of .wdaccess files (see "Opening and Restricting Access", below).
Hosting Dashboard and Instance Splash page
...
<instance-name> |
| |
| htdocs | The root/Home for your application or website |
| confs | Customer created/modified apache configuration files (apache include files) |
A note on layouts
Roughly speaking, a hostname like yoursite.cit.cornell.edu will point to a folder on the filesystem, so that visitors of http://yoursite.cit.cornell.edu will see the contents of that folder.
One way to layout is to use subfolders to organize your site, rather than to put all of your pages in the base /htdocs directory. Your splash page will show information like:
Home Directory
Using getenv("DOCUMENT_ROOT") shows /infra/lamp/cust/lampuser1/htdocs.
Organizing your site into folders like...
htdocs | ||
| yoursite1 | |
|
| index.php |
|
| stuff.jpg |
| yoursite2 | |
|
| index.php |
|
| yoursite2.php |
|
| morestuff.jpg |
| yoursite3 |
and so forth allows to have multiple sites "living" in the same instance with virtualhosts configured to use slightly different document_roots (http://yoursite1.cit.cornell.edu
points to htdocs/yoursite1/; http://yoursite2.cit.cornell.edu points to htdocs/yoursite2/; and so on).
However, you are of course free to organize your site in the best way possible for you. The new Cornell Stack also allows for multiple LAMP like instances in a Shared-Apache configuration. Please see {Small sites or apps|https://confluence.cornell.edu/x/kgz_DQ] as an example. To find out more on the Shared Apache, please see Introduction to CIT Hosting Services Cornell Stack#shared
Git/Mercurial files - EXPERIMENTAL
...