Deploy New

Click the "Deploy New" button to Upload a new Application Archive for deployment.

Fill out any necessary information then click "Continue" to proceed.

Once successfully deployed, an Icon symbolizing the deployed application will be added to the Canvas display.

JAVA

The JAVA application must be in WAR format. The expanded directory tree should look like:

. ..

WEB-INF

NOTE: If available, a Database is automatically created for the application to use and the

DataSource (if the name is specified) is configured.

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/java/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/java/webapps/myapp

NOTE:For GlassFish, apps are deployed under the Glassfish "autodeploy" directory.

NOTE:For JBoss, apps are deployed under the JBoss "deploy" directory.

RAILS

The RAILS application must be in ZIP format. The expanded directory tree should look like:

-app -config -db -doc -lib -log -public -script -test -tmp

-vendor

NOTE: If available, a Database is automatically created for the application to use and the

"production" database configuration is populated in the database.yml file.

db:migrate is automatically run on the application upon deployment.

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/rails/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/rails/webapps/myapp

GRAILS

The GRAILS application must be in ZIP format. The expanded directory tree should look like:

-grails-app -lib

-scripts

NOTE: If available, a Database is automatically created for the application to use and the

"production" database configuration is populated in the DataSource.groovy file.

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/grails/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/grails/webapps/myapp

NOTE: You may deploy a GRAILS application as a JAVA WAR, however in order for the

DataSource be set, you would need to specify the data source's JNDI name in the grails-app/conf/DataSource.groovy file as follows:

dataSource {

jndiName = "java:comp/env/jdbc/myDataSource"

# or

# jndiName = "java:comp/env/myDataSource"

}

NOTE: Also if the GRAILS app is deployed as a regular JAVA application, you may need to upload the

Database Schema.

Play

The Play application must be in ZIP format. The expanded directory tree should look like:

-app -conf -public

NOTE: If available, a Database is automatically created for the application to use and the

"production" database configuration is populated in the application.conf file.

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/play/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/play/webapps/myapp

Scala/Lift

The Scala/Lift application must be in ZIP format. The expanded directory tree should look like:

-src -project

NOTE: If available, a Database is automatically created for the application to use and the

database configuration is populated in the default.props file like so:

src/main/resources/props/default.props

The application is deployed to:

<HOME_DIRECTORY>/scalalift/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/scalalift/webapps/myapp

Django

The Django application must be in ZIP format. The expanded directory tree should look like:

-app

-settings.py -...

NOTE: If available, a Database is automatically created for the application to use and the

"default" database configuration is populated in the settings.py file.

And the "syncdb" command is executed.

During installation of Django apps, a superuser is created. Below are the default credentials:

User: admin

Password: coolgeek Application Directory

The application is deployed to:

<HOME_DIRECTORY>/django/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/django/webapps/myapp

Railo (CFML)

NOTE: You can also install Railo as a regular JAVA Application (see above).

The Railo (CFML) application must be in ZIP format.

The expanded directory tree should look like:

. ..

whatever.cfm

NOTE: If available, a Database is automatically created for the application to use and the

DataSource configuration is set.

NOTE: For security purposes (as well as for a loadbalanced cloud environment), the Railo admin console is unavailable by default.

To enable, remove the security constraint in the WEB-INF/web.xml file.

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/railo/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/railo/webapps/myapp

NOTE:For GlassFish, apps are deployed under the Glassfish "autodeploy" directory.

CfWheels

The CfWheels application must be in ZIP format. You only need the CfWheels project files.

You do not need to bundle CfWheels - that is automatically done for you at deployment.

The expanded directory tree should look like:

.

NOTE: If available, a Database is automatically created for the application to use and the

DataSource configuration is set. The DataSource name is set to "wheels".

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/cfwheels/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/cfwheels/webapps/myapp

NOTE:For GlassFish, apps are deployed under the Glassfish "autodeploy" directory.

NOTE: You can also install CfWheels as a regular Railo (CFML) Application (see above).

PHP/Zend

The PHP/Zend application must be in ZIP format. The expanded directory tree should look like:

-application -public

NOTE: If available, a Database is automatically created for the application to use and the

"production" database configuration is populated in the application.ini file.

Application Directory

The application is deployed to:

<HOME_DIRECTORY>/zend/webapps

So an application named myapp would be in the following directory:

<HOME_DIRECTORY>/zend/webapps/myapp

NOTE: If deploying a PHP application not using the Zend Framework, place the PHP files in a directory called "public" before archiving the application.

NOTE: For PHP applications deployed with Quercus, refer to the JAVA section.