This page is designed to walk you through some of the features and areas of your Cornell Stack VM and space.
Suggestions are always appreciated, so please let us know if there is material that is unclear, could be improved, or additions that we should make to this page. Thank you!
By default, your new Cornell Stack and instance(s) will come with a new CUWA permit or Active Directory "permit" group 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
Once your Hosting Virtual Machine (VM) has been created and instance(s) set up, you can access information and the VM from the Hosting Dashboard via https://dashboard.hosting.cornell.edu. This is a one stop shop to controlling services on your VM (yes you can stop and start your instances), as well as finding specific information about your instance(s). The Hosting Dashboard should list all VM's you have access to based on the AD Group or Permit that's been assigned to them.
The Cornell Stack continues to support Webdav access to upload/modify/delete the files for your website/application. The access URL previously used for Hosting services in Coldfusion 9 and LAMP2 are not valid for Cornell Stack access. The webdav url is specific to the VM your instance(s) lives on.
The Webdav client you use is entirely up to you, but it must support HTTPS/Secure Connections. CIT does not have a recommended Webdav client, but the ones we have success with are:
Depending on what services you are running, once you've successfully connected with your webdav client, you should see something similar to the following:
<instance-name> |
| |
| htdocs | The root/Home for your application |
| jars | Directory for customer to upload/install new/additional jar files, like database drivers or custom built jars |
| server10 | Coldfusion instance settings and configurations. Tread lightly here - modifications in this area could break the Coldfusion install |
| confs | Customer created/modified apache configuration files (apache include files) |
<instance-name> |
| |
| htdocs | The root/Home for your application or website |
| confs | Customer created/modified apache configuration files (apache include files) |
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
If you requested to have git or mercurial installed and setup on your VM and instance, you will see additional subdirectories like "repos", "git", or "hg". For more information on version control options and setup, please see GIT Info or Mercurial Info.
The Cornell Stack allows mulitple holding ID's to permit and restrict access across applications living on the same VM. This is ideal for those customers who may want to host multiple instances on one VM but provide more isolation between the applications. Utilizing and changing the holdingIDs and file permissions should be reserved for experienced web developers and those knowledgable in Linux file permissions.