Campsite 2.3 User Guide

Campsite 2.3 User Guide

Select your language:  
    Search:   
<2.1. Requirements and Dependencies        2.2.1. Using the configure command to customize Campsite install>

Print / Download:
Available languages: english Last update: 2005-10-29 15:06:08

2.2. Installation Steps

Table of Contents
2.2.1. Using the configure command to customize Campsite install
2.2.2. Installing Campsite as a non-root user
2.2.3. Configure the Web Server
2.2.4. Configuring Campsite to Work Over SSL
2.2.5. Upgrading from Versions 2.2.x
2.2.6. Upgrading from Versions 2.1.x
2.2.7. Installation Compatibility Issues
2.2.8. New Template Statements and "Short Name" URLs

Here is what you need to do to install Campsite:

  1. Copy the Campsite archive in a directory on the server.
  2. Unarchive it using the command: tar xzvf <Campsite_archive>.
  3. Enter Campsite directory.
  4. Run './install', answer the install questions.

When you run the install script, you have the option of customizing certain aspects:
  • The default apache user/group: the administration interface scripts and template will belong to the apache user/group; when creating a new instance the script will use the default values unless instructed otherwise by the user.
  • Campsite install directory: the default value is /usr/local/campsite
  • Campsite binary directory: the default value is /usr/local/campsite/bin
  • Campsite configuration directory: the default value is /usr/local/campsite/etc
  • Campsite WWW directory: the default value is /usr/local/campsite/www; this is the place where new instances will be installed.
  • Campsite binary directory: the default value is /usr/local/campsite/www-common; this is the place where administration interface scripts were installed.
  • Default SMTP server address: localhost; this is the address of the email server.
  • Default SMTP server port: 25; this is the port of the email server.
  • Parser start port: 2000; the new instances will be assigned socket ports starting from 'start port' value + 1

Installing on Fedora Core 4 or CentOS
There is an issue when installing on Fedora Core 4 and CentOS. The issue is following:
when using PHP5 (which is default on these OS), Pear has a corrupted File module and it cannot be installed by standard way.
More info: http://pear.php.net/bugs/bug.php?id=5071

This problem is fixed in the sources repository and in bug discusion is how-to do that.

To fix:
1) Download a fixed version of the File package here.
2) Type as root: "pear install File-1.2.2.tgz"
3) Process the install of campsite 2.3.x or other application that needs pear and File module.

On CentOS, you must disable pear install from the Makefiles, but on Fedeora Core 4 it works without modification.

 


add a note add a note User Contributed Notes
2.2. Installation Steps
Slobodan Gogic  slobodan dot gogic at mediaonweb dot org
Wednesday 28th of December 2005 03:30:00 PM
I have had some problems installing it on Suse 9.3.

I had to edit configuration file so that check for apache config files are not executed...

First check NamedVirtualHost settings. It needs to be enabled.

If that doesnt work then try this:

I assume that its Apache2 so, what I have done is this:
in the ".install_conf" directory find file check4_functions, open it in edit mode, and find

user_line=`grep -h -E "^[[:space:]]*User[[:space:]]+" ${conf_files} 2>
/dev/null`
if ["$user_line"=""];then
echo "Invalid apache configuration files. Aborting"

This is one of 2 checks that fails under Suse. I think that first one checks apache user name, and other apache group. So just edit

if["$user_line"=""]

to

if["$user_line"="1"]

(since user_line will not return value 1 check will be ok).
Do this again for the second check with $group_line...

Afterwards, you might have some more errors due to different locations of libraries on Suse distro, but just add them in search path in check4_functions file. Now, I know that this "hack" is sooooo lame, but actualy I dont care since it works, at least worked on my machine.
:)

Dave  
Thursday 03rd of November 2005 10:18:00 PM
In case anyone wants to install on fedora core 1. Its very simple, just a few extra steps.

My server:
Fedora core 1
MySQL 4.0.21
PHP 4.3.*

I had to install libidn-0.5.9 Very straightforward install. Get it here: http://josefsson.org/libidn/releases/

After install libidn, I ran the install again and got a few file permission errors. The install_log explain it all.

After fixing file permission, I tried to hit mysite.com/admin and got file not found errors. Paul explained to me I was missing PEAR libraries and explained how to install them:

pear install FILE_NAME

I had to install:
File
File_Find
Net_URL
Net_Socket
HTTP_Request
HTTP_Client

Hit mysite/admin again and everything is working great.

Doug Arellanes  
Wednesday 12th of October 2005 05:19:00 PM
How to remotely upgrade a Red Hat 9 server to a Fedora Core server:

I don't know if you're in a similar situation, but we have one server in a hosted facility in the US that was running RH9. We need to upgrade its Campsite install to 2.3, but as you know, there are problems with that. So we first have to upgrade the server from RH9 to FC4, and doing so remotely was something we didn't know much about.

Luckily, we found a page that explained the process. The page is at:

http://www.brandonhutchinson.com/Upgrading_Red_Hat_Linux_with_yum.html

There are some issues not described in this document, so go through this one too:

http://www.ldeo.columbia.edu/~vschmidt/notes/redhat2fedora/index.htm

<2.1. Requirements and Dependencies 2.2.1. Using the configure command to customize Campsite install>

  Last update: 2005-10-29 15:06:08
Website powered by Docmint Last update: 2005-10-29 15:06:08
Total page time: 0.877208948135