Page History

...

Every LAMP hosting site starts out with a directory structure much like this:

admin/

This is the "administration" area of your site. It is restricted via CU WebAuth to the permit created for you when your instance is created, and to the CIT LAMP support staff's permit. Currently it contains a couple of utilities designed to make managing your LAMP site easier.

phpMyAdmin

phpMyAdmin is one of the most popular browser-based MySQL management programs. You can do pretty much anything from phpMyAdmin that you could do from any other MySQL management application. Some administrative actions, such as creating a new database, are permissions-restricted for security reasons; otherwise, you should have full access to edit and maintain the database that is provided for you when your instance is created.

Documentation and information about phpMyAdmin is available at their website. Any additional questions or database requests should be sent to the DBA team.

wdaccesseditor

This is a utility for editing and configuring any CUWebAuth or Apache-based access control file on your site. It also provides an example/template of the access control directives for using CUWebAuth to control permissions to your site.

...

...

cgi-bin/

This is the legacy traditional cgi-bin directory for placement of Perl or Python CGI scripts. There are two example CGI scripts available from the splash page to provide environment information and to provide a quick "getting started" example.

styles/

This is the stylesheet directory for the Cornell Identity styles as provided from the Visual Identity Site. They are used as part of the splash page, though you of course are free to add your own, use a different style or remove the directory entirely.

index.php

The default index file in your document root is the splash/information page you see when you visit your staging URL provided at account creation. This page is full of links and information for using the environment, getting more help and documentation, and to provide information about your instance and its configuration.

If you do not plan on using CGI it is strongly recommended that you delete this folder/directory

Getting connected to upload content

...

More details for getting set up with WebDAV in Windows network places are available here.

General directions for Windows and Macintosh are available here.

If you prefer, there are also several excellent third-party applications available for WebDAV connections, particularly for Macintosh, including Cyberduck, Transmit, Coda, Goliath, and more. Windows support at the moment is primarily limited to the Network Places folders provided within the operating systemFor Windows the alternative to Network Folders is BitKinex.

Permits and Access Control

Instance Permits

By default, your LAMP account 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>*. 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).

Opening and Restricting Access

Please see the guide available here.

Adding additional pages to your site

...

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^{Image Removed} will see the contents of that folder.

...

When you are ready to add or move additional URLs like yoursite.cornell.edu to point at your site, please submit a request to webservices-l, with at least a day or two of notice to ensure that we have time to coordinate DNS moves and configuration updates. If you are moving an existing URL, the more notice you can provide, the better.

...

A note about Content Management/Blogging Systems (WordPress, etc.)

Before installing Wordpress in the LAMP hosting environment, please chect out the Cornell University Blog service at http://blogs.cornell.edu/

Several content management systems have internal configuration that specifies what the software thinks the URL/hostname of the site is. If you have setup the CMS using the pre-production URL but intend to have a custom URL point to it later, you will need to change the configuration later.

...

Using CU Web Auth to open or restrict access to your application: Confluence