-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
Coldfusion 8+ (must be running as a user with access to the file system, see below) (Has been tested with 8,9 and 10) Windows/OS X/Linux - has been tested on all three
Cascade is intended to be installed at the web root on all of your servers. You will have a separate installation for each server. If installing using git, cd to your web root then run the clone command. If downloading a zip, extract the Cascade folder into you web root. If done properly you should be able to access it with a URL such as http://localhost/cascade (just swap localhost with the name of your server). Once you have this folder in the right place navigate to that URL in your favorite browser.
Note: it is possible to install cascade to a folder named something besides cascade, you just need to edit the value of the variable application.settings.appBaseDir in Application.cfm. This has not been a completely tested feature right now though so do so at your own risk.
If you are running Cascade for the first time you should see the initial configuration screen. Before filling out this form, you should go ahead and create a couple of folders on your server.
You need two folders, one is where the archives will be stored, and one is the folder for the Derby database. It is suggested to put these folders somewhere outside of the web root where their contents are not able to be accessed by a browser, purely for security reasons. If you aren't concerned about security you can place them anywhere you want. I created a folder right above my web root called Cascade and created two subfolders, archives and db. Wherever you decide to put them, they need to already exist before you submit the configuration form.
Most of the fields in the form are self explanatory, so I will only mention the ones that need further explanation.
- server name: Puck this name carefully. It should be unique to this server only. All archives built on this server will reference this name, and it is also used to identify remote servers.
- CF Admin Password: this is only used to create the derby db and the dsn that points to it. It is not stored anywhere and is not held in any persistant scope. Once the configuration file is created, there is no need for the cf administrator privileges.
- archive directory: this directory must already exist before submitting this form. This is where the archive files will be stored locally. It can be any directory that the coldfusion service has authority to read and write from. If you expect that you might be using cascade a lot, you might want to put this on a mounted network share. Just make certain that the user that CF is running as has authority to that directory.
- derbyDB Database Directory: this directory must also already exist before submitting the form, but a directory will be created beneath it that is the same name as the derby database name you entered. For instance, if you say to put the database directory at c:\derbydb, and you named the derby database name "cascade", c:\derbydb must already exist, and the application will create c:\derbydb\cascade for you and create the database there.