-
Notifications
You must be signed in to change notification settings - Fork 24
/
Install.txt
68 lines (53 loc) · 3.82 KB
/
Install.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
**************************************************************
See Install-binary.txt if you're just installing the binaries.
**************************************************************
**************************************************************
From version 2.0.0, Cuyahoga requires the .NET 3.5 Framework.
**************************************************************
Installing Cuyahoga from source.
1. Unzip the files to a local directory.
2. Create a database. Supported databases are:
- SQL Server 2000-2008 / SQL Server Express 2005-2008
3. Build and run.
There are 2 possible ways to build Cuyahoga: using Visual Studio 2008 or NAnt.
3a. Building with VS 2008.
- Make sure that you have VS.NET 2008 SP1 and ASP.NET MVC 1.0 installed
- Go to the /src directory and Open Cuyahoga.sln with VS.
- Build Solution.
- Change the connection string in Web/Config/properties.config (connectionString)
to the database that is created in step 2.
Example (SQL Server):
<connectionString>server=(local);database=Cuyahoga;uid=***;pwd=***;</connectionString>
Example (PostgreSQL):
<connectionString>server=192.168.0.1;port=5432;database=Cuyahoga;uid=***;pwd=***;</connectionString>
Make sure that the account that connects to the database for the first time has enough
permissions to create the database!
3b. Building with NAnt.
- Open a command prompt, go to the directory where you extracted the .zip file.
- Enter 'build'. This will create a build directory with the compiled binaries and the
libraries (for example 'build/net-3.5/debug').
- Enter 'build deploy' to add the other files needed to run Cuyahoga to the build.
- Create an IIS application that points to the build directory or copy the files in the
build directory to the root directory of an existing IIS application.
- Change the connection string in the Web/Config/properties.config (connectionString)
to the database that is created in step 2. See 3a for example connection strings.
You are now ready to run the application. At the first visit, the database will be installed automatically,
and you'll be asked to set a password for the administrator (min. 5 characters!).
After that there is a choice to install additional modules and to create a sample site.
When everything is finished you can visit the web site adminstration pages. The url of the
web site administration is http://SERVER_NAME/VIRTUAL_DIRECTORY/manager/.
If you installed Cuyahoga in the cuyahoga virtual directory on your localhost, this url will be
http://localhost/cuyahoga/manager/.
The following steps are only required when no sample site is installed.
In the web site administration, the first thing to do is creating a site. Make sure that the
site url that you enter, corresponds with the real site url, including the virtual directory
(for example, http://localhost/cuyahoga).
When a site is created you can start adding pages and sections. Just give it a try
and when something isn't clear, check the forums at http://www.cuyahoga-project.org/home/forum.aspx.
Hints and tips:
- It's possible run the database install scripts manually if the installation fails for some
reason. They are located in the /Web/Install/Database directory.
- The /SiteData directory must be writable for the ASP.NET user (NETWORK SERVICE on IIS). This is the directory
where the content files, search index and templates are located.
- You can enable logging to uncomment the <log4net> section in the Config/logging.config. Make sure your
ASP.NET user has write access to the path of the logfile.