Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Every ColdFusion VM site starts out with a directory structure much like this:

"applicationNamecustName/appName"/

 

htdocs/

 

  index.cfm

 

 

splash.cfm

 

jars/

 

server/

 

styles/

htdocs/

...

splash.cfm

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.

  • WebDav urls: The kproxy or DAVPortal urls you can use to modify your site files
  • 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. More information about using ht/wdaccess files is available at the ht/wdaccess page.
  • Webserver Logs: index listing of access and error logs for apache
  • ColdFusion Administrator: link to the CF Administrator site to manage this Coldfusion instance.
  • Other useful links

CF StatusUtilities/Self-service
One of the tabs at the top of the splash page links you to a Status/Self-service area. It is restricted via CU WebAuth to the permit created for you when your instance was created, and to the CIT ColdFusion support staff's permit. Currently it contains a couple of utilities designed to make managing your ColdFusion site easier.

...

Your ColdFusion splash page , available by default at the staging URL provided when your instance is created, has the links you need to access your instance's WebDAV connection.

...

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 system.

...

By default, your ColdFusion account will come with a permit of the form cit.lampcoldfusion.*. 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 permit interface at http://paw1.cit.cornell.edu/cgi-bin/permit.cgi

...

A recommended 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 Using getenv("DOCUMENT_ROOT") shows /infracoldfusion/lampjvms/cust"custName/lampuser1appName"/htdocs/.

Organizing your site into folders like...

htdocs

 

splash.cfm

 

yoursite1

 

 

index.php cfm

 

 

stuff.cfm

 

 

pic.jpg

 

yoursite2

 

 

yoursite2 index2.php cfm

 

 

morestuff.jpg

 

yoursite3

. . .
and so forth. This allows for your provided staging splash page URL (something like yoursite-lampcf###.citserverfarm.cornell.edu:8001/splash.cfm) to remain an "information area" launchpad with the splash page and administration area in /admin, and allows you to easily organize and configure several sites within your instance.

However, you are of course free to organize your site in the best way possible for you; this is just a suggested layout based on successful site development and organization in other hosted environments here at CIT.

Adding additional URLs

*** UPDATE????Self-service somewhere

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.

...