forked from cuyahogaproject/cuyahoga-1
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Install-binary.txt
78 lines (58 loc) · 3.89 KB
/
Install-binary.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
69
70
71
72
73
74
75
76
77
78
**************************************************************
From version 1.5.0, Cuyahoga requires the .NET 2.0 Framework.
**************************************************************
Installing Cuyahoga from the binary distribution
1. Requirements
- IIS 5.0 or higher
- The 2.0 runtime environment.
- A database server. Supported databases are
- SQL Server 2000 / SQL Server 2005 / SQL Server Express / MSDE 2000
- PostgreSQL 7.4 and higher
- MySQL 4.0 and higher
2. Extract the files to a directory on your local machine.
3. Create an empty database.
4. Change the connection string in the /Config/properties.config (connectionString)
to the database that is created in step 3.
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!
5. Create a website or a virtual directory in IIS and set its home directory to the physical
directory where the Cuyahoga files were extracted.
6. You are now ready to run the application. Open your browser and navigate to the site or virtual
directory that is created in the previous step.
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/Admin/. If you installed Cuyahoga in the cuyahoga
virtual directory on your localhost, this url will be http://localhost/cuyahoga/Admin/.
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 (nodes) 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 /Install/Database directory.
- The search index has to be in a folder that is writable for the ASP.NET user. You can specify the
folder in the web.config:
<CuyahogaSettings>
...
<add setting="SearchIndexDir" value="~/index" />
<add setting="InstantIndexing" value="true" /> <!-- true/false -->
</CuyahogaSettings>
InstantIndexing indicates that when you edit the content of a module that is searchable, the
search index will be updated immediately. If you turn this off, you have to manually index the
content from the Administration section.
- You can enable logging to uncomment the <log4net> section in the Web.config. Make sure your
ASP.NET user has write access to the path of the logfile.
- Give the ASP.NET user write access for the Web/UserFiles directory to enable uploading images or
other files with the FCKEditor from the StaticHtml and Articles modules.
- Give the ASP.NET user write access for the Web/files directory to enable uploading files with
the Downloads module. You can optionally enter a physical path for the location where the files
should be uploaded. With this, it is possible to keep the files out of the web site to prevent
direct downloading.