Getting Started

Setting Up StoryVerse

To begin using StoryVerse you must install the application on a web server and set up a database. Then you must initialize the database, which StoryVerse does for you. Here are the steps:

1. Set up a web application in IIS using ASP.NET 2.0
2. Configure the web application to recongnize .rails extension. here's how
3. Build the solution in Visual Studio. (NOTE: The first time you open the solution you might notice that some linked connections.config files are "missing." The first time you build, connections.config is created under the Solution Items folder, and the links will no longer be missing.)
4. In Visual Studio, open the connections.config under Solution Items. Modify the connection strings per your environment. The connection string named DbVerse is used for database creation and updates and therefore must have permission to create and drop most database objects.
5. Publish the solution to the location you set up in step #1
6. In the publish location, open Web.config, and modify as follows:
• In the

  <activerecord>

  section, modify the hibernate.connection.connection_string_name key to point to the proper named connection from connections.config.
• In the

  <monorail>

  section, modify the smtpHost attribute to point to an accessible SMTP server. This will enable delivery of notification emails.
7. Run InitializeDatabase.bat in the trunk folder. (See note instructions below for remote databases.)

These steps cover the intial setup of the database. Future versions might require applying database updates.

Remote Database

If your database is not reachable from your solution trunk you must copy the contents of the Debug folder of StoryVerse.DbBuilder.Console to a location that can reach the database. You will also need to copy InitializeDatabase.bat to that location and possibly edit it to so the execution path points to StoryVerse.DbBuilder.Console.exe.

Note To Developers

You might also want to go ahead set up the Acceptance Test project. At present, this project is pretty much just a placeholder. To set it up, edit the app.config file in the same manner as described above for the WebUI project. Then once you do that, maybe you can write a bunch of acceptance tests!! :)