With emerge of Gnome Shell (3.x series), there have been some changes with gnote, and which are inconvenience to old gnote users. These changes are below:

1. Gnote status icon not visible: It is because the gnome shell does not have any panel where you can add any applet/icons.
2. Lack of Gnote default menu interface: In previous versions, when you access gnote through the applet icon, you would have seen a list of your old notes and menu items to create new note or search existing notes. This is no more the case with default gnote installation. If you launch gnote, you’ll see the “Search all Notes” window.
3. Gnote not triggered up on startup: The previous versions of Fedora and/or other GNU/Linux distributions used to fire-up gnote applet program on startup, but this does not happens now. So every time you need gnote (and assuming that you’ve closed previous gnote windows), you’ll have to open gnote from the applications menu (or from command).

The solution to these problems are easy enough, and are available on Gnote Help documentation under the FAQ section. To solve all these aforementioned problems, follow these steps:

• Open Terminal, and enter into root account.
• Enable the gnote icon through gsettings:

: gsettings set org.gnome.gnote use-status-icon true .

• This command will now persistently display gnote icon in the bottom right panel of gnome shell if gnote is fire up, and will not vanish even if you close any open gnote window.
• Now you need to set gnote to fire at start-up. In previous versions, you could have done through Startup Application preferences. But this item is not directly available under applications nor under System Settings. So you’ll have to use terminal to fire-up this application:

gnome-session-properties

• A Start-up preference dialog box will open up. Click on the Add button.
• Put “Gnote” as the name, “/usr/bin/gnote” as the command, and “Gnote – Gnome’s note taking application” as the comment. (Note: You can put anything in the name and comment section).

Add Gnote to Startup

• Click on Add button.
• This will add gnote to startup. So from the next time you open up your linux box and log in, you’ll see gnote status icon visible in the bottom right panel.

Installing and using new gnome-shell theme

• Create a .themes directory in your home.

mkdir ~/.themes/

• Download the desired theme, extract it, and put the resulting directory into ~/.themes/. Note that you can put any number of theme sub-directories into the ~/.themes directory.
• Install User Theme gnome shell extension.

sudo yum -y install gnome-shell-extension-user-theme

• Now install Gnome Tweak Tool.

sudo yum -y install gnome-tweak-tool

• Open Gnome Tweak Tool, and click on the Shell Extensions item in the left pane. On the right pane click on the toggle button next to User Themes Extension to enable the extension. Close the window.
• Reload Gnome Shell. Press [Alt]+[F2], type r, and press [Enter].
• Open Gnome Tweak Tool again, and click on the Theme item in the left pane. On the right page, you’ll see a list of available gnome-shell themes in a drop down box. Select the theme that you want to activate.
• Enjoy the theme that you applied.

The problem with the current version

With the current setup, gnome tweak tool will report “Shell user-theme extension not enabled.” This might be due to version mismatch between gnome shell (3.2.1) and user theme extension (3.2.3). See the screenshot below (you need to hover on the orange notification icon to see that message).

Gnome Tweak Tool Theme Problem

Temporary Fix

To fix this problem, you’ll have to change the dconf settings manually. This requires you to know the name of the theme folder in advance. As of example, if you want to set Faience as your default gnome shell theme, and there is a directory named Faience in ~/.themes/ (e.g. ~/.themes/faince), then you need to remeber the name faince (remember that you need to remember the name of the directory and it’s case sensitive).

• Install DConf Editor.

sudo yum -y install dconf-editor

• Open DConf Editor. You’ll see a list of hierarchical controls (in a tree-view) in the left pane, and relevant settings of the selected node on the right pane.
• Expand to org > gnome > shell > extensions > user-theme on the left pane. On the right pane you’ll see a key-value pair field with the key named “name”. Double click on the value field for that key, and type the name of the theme directory (e.g. faience in this case).
• After you set the value, close the editor. You’ll now see the required gnome shell theme.

ZCS does not natively support Procmail, and hence there are 3 ways to use procmail with ZCS:

1. Use ZCS with a MTA set to a server/installation with procmail configured (e.g. ZCS has a MTA set to another machine which has postfix with procmail configured and all the filtering is done by that server)
2. Use ZCS as normal, and run procmail on your mailbox (through the procmailrc file), to do the sorting/filtering.
3. Use ZCS with procmail as a pipe for mail delivery. (This guide will discuss this way of using procmail.)

Let’s assume:

• The mail server with ZCS has already been installed and configured. If not, check my ZCS installation guide and install ZCS.
• We want to use procmail to filter all emails.
• We want to discard emails with attachments that are destined for outside of our domain (i.e. test-example.com), but allow email with attachments for inside our domain.
• We are using a CentOS 6 machine (works on Fedora, RHEL as well).
• sudo is configured for the user or we are executing commands as root user.

Install Procmail

sudo yum -y install procmail

Set ZCS Transport Map

• Login as zimbra user.

su - zimbra

• Check the currently configured transport map for postfix:

cat /opt/zimbra/postfix/conf/main.cf | grep transport_maps

The output should look like:

transport_maps = proxy:ldap:/opt/zimbra/conf/ldap-transport.cf

• Add the transport file to the zimbra configuration.

zmlocalconfig -e postfix_transport_maps=' hash:/opt/zimbra/postfix/conf/transport,proxy:ldap:/opt/zimbra/conf/ldap-transport.cf'

• Add procmail pipe to the transport file (requires to edit the file as root user).

su -
vim /opt/zimbra/postfix/conf/transport

Add the following content to the file:

*    procmail-pipe

• Create the db file for the transport map.

su - zimbra
postmap /opt/zimbra/postfix/conf/transport

• For the pipe to work, a corresponding set of configuration needs to be done in the postfix’s master.cf file. In this case master.cf.in file.

vim /opt/zimbra/postfix/conf/master.cf.in

Add the following text at the end of the file:

procmail-pipe    unix    -    n    n    -    -    pipe
flags=    user=zimbra    argv=/usr/bin/procmail /opt/zimbra/procmail/procmailrc

Create the Procmail Recipe

• Create the Procmail recipe file (i.e. /opt/zimbra/procmail/procmailrc file that we have configured in the previous step).

mkdir /opt/zimbra/procmail/
cd /opt/zimbra/procmail/
touch procmailrc
chown -R zimbra:zimbra .
vim procmailrc

Add the following content to the file:

SHELL = /bin/sh
PATH=$HOME/bin:/usr/bin:/bin:.
MAILDIR=/opt/zimbra/procmail/ # You better make sure it exists
DEFAULT=$MAILDIR
LOGFILE=.procmaillog
LOCKFILE=.procmaillock
VERBOSE=yes

:0
* !To:.*test-example\.com.*
* ! ^Content-Type:.*text/plain.*
{
:0B
* ^(Content-(Type|Disposition):.*|[ ]*(file)?)name=("[^"]*|[^]*)\..*
/dev/null
}

• Restart Postfix.

zmmtactl stop
zmmtactl start

Thanks to the Zimbra forum entry and Zimbra Wiki on Configuring Postfix to work with piped scripts from where I adapted my installation and hence wrote this guide.

Further Reading

• Postfix Dedicated Transport Howto
• Configuring Postfix to work with piped scripts - Zimbra :: Wiki
• Postfix manual - transport(5)
• Zimbra and procmail - Zimbra :: Forums

CentOS Version: 6.0 x86_64
ZCS Version: 7.1.3 GA 3664 for RHEL 6 x86_64 Open Source (Release 7.1.3_GA_3346.RHEL6_64_20110928134428)

This guide will take you through installing Zimbra Collaboration Server (ZCS) which is an integrated bundle of Mail Server, web-documents, and other collaboration services enriched with easy web-administration interfaces. This makes ZCS a good choice for those who do not want to install and configure all the tools and service needed to support the features required for email, and web administration + web-mail interface is quite a time and effort saving feature of ZCS.

This guide makes a few assumptions about the prerequisites that have already been made/configured/handled:

• The server will handle email for the domain test-example.com.
• The server will be hosted on a machine named mail.test-example.com.
• The DNS is properly set up for resolving the names, and as well as for the MX record for test-example.com.
• The machine for mail server has access to the DNS server and can resolve names.
• The installer for ZCS (RHEL 6) has been downloaded.
• The mail server has access to the Internet (for installing/updating packages, as well as to contact external relay MTA)
• sudo is configured for the user, or the commands are used as root user.

Pre-Installation Tweaks

• Disable system installed postfix/sendmail as ZCS runs its own postfix. System-wide installed postfix/sendmail interferes with ZCS’s postfix.

sudo service postfix stop
sudo chkconfig postfix off
sudo service sendmail stop
sudo chkconfig sendmail off

• Install nc package

sudo yum -y install nc

• Disable SELinux (I’ve not yet found a way to use ZCS with SELinux on).

vim /etc/sysconfig/selinux

In the file, set:

SELINUX=disabled

sudo setenforce 0

• Allow a few ports for Zimbra beforehand (not required before installation, but makes no harm in pre-setting it)

sudo iptables -I INPUT -p tcp --dport 443 -j ACCEPT #HTTPS
sudo iptables -I INPUT -p tcp --dport 3930 -j ACCEPT
sudo iptables -I INPUT -p tcp --dport 110 -j ACCEPT #POP3
sudo iptables -I INPUT -p tcp --dport 143 -j ACCEPT #IMAP
sudo iptables -I INPUT -p tcp --dport 993 -j ACCEPT #IMAPS
sudo iptables -I INPUT -p tcp --dport 389 -j ACCEPT #LDAP
sudo iptables -I INPUT -p tcp --dport 995 -j ACCEPT #POP3S
sudo iptables -I INPUT -p tcp --dport 7025 -j ACCEPT
sudo iptables -I INPUT -p tcp --dport 5800 -j ACCEPT
sudo iptables -I INPUT -p tcp --dport 5900 -j ACCEPT
sudo iptables -I INPUT -p tcp --dport 7071 -j ACCEPT #Port for ZCS Web Administration
sudo iptables -I INPUT -p tcp --dport 3894 -j ACCEPT
sudo iptables -I INPUT -p tcp --dport 3895 -j ACCEPT
sudo iptables -I INPUT -p tcp --dport 80 -j ACCEPT #HTTP (for webmail) 

• Fix the hosts file.

vim /etc/hosts

Put the name of the machine (i.e. mail.test-example.com) in the hosts file (assuming that the IP of the machine is 10.0.0.253):

10.0.0.253    mail.test-example.com mail

The hosts file should look like this:

127.0.0.1    localhost localhost.localdomain localhost4 localhost4.localdomain4
::1          localhost localhost.localdomain localhost6 localhost6.localdomain6
10.0.0.253   mail.test-example.com mail

Install ZCS

• Deflate the installation archive (in this case zcs-7.1.3_GA_3346.RHEL6_64.20110928134428.tgz file).

tar -zxvf zcs-7.1.3_GA_3346.RHEL6_64.20110928134428.tgz

• Start the installation:

cd zcs-7.1.3_GA_3346.RHEL6_64.20110928134428
./install.sh --platform-override

• You’ll be asked various questions during the installation, use the default or obvious answers.
• Before completing the installation and writing configuration parameters to the configuration file, you’ll be prompted to review the settings or to fix some unset configuration. At this step, make sure you set the password for the admin user. It has a menu based approach. After reviewing/setting configuration, get out of the screen and save the configuration.
• Let the installer do the rest of the configuration, at the end of which you will be notified of the completion of the installation.

Access Zimbra Collaboration Server

The default location of ZCS installation is /opt/zimbra/, and the installer configures a init.d/service script through which you can stop, start, restart and check the status of ZCS. All zimbra components and daemons run as user zimbra. ZCS Administrative web-interface is available at 7071 port and the webmail runs at the default http port (i.e. port 80) of the machine. For this instance, the administrative interface would be available at http://mail.test-example.com:7071 and the webmail would be available at http://mail.test-example.com.

Conventions

• [Square braces] are used to denote keystrokes.
• “Quotes” are used to denote values and keywords.

Introduction

Fez is an open source project to produce and maintain a highly flexible web interface to FEDORA for any Library or Institution to configure and publish or archive documents of any type sustainably. Fez is a PHP / MySQL front end to the Fedora repository software. It is developed by the University of Queensland Library as an open source project hosted on SourceForge.

Install Prerequisites

Apache Web Server

yum install httpd

PHP

yum install php php-devel php-gd php-mysql php-pgsql php-xml

MySQL Database Server

yum install mysql mysql-server libdbi-dbd-mysql mysql-connector-odbc mysql-devel

Other image manipulation tools

yum install ImageMagick poppler poppler-utils libpng-devel

Additional Libraries (php-tidy & libtidy)

yum install libtidy php-tidy

Graphviz

yum install graphviz

To correctly run graphviz, execute:

dot -c

ExifTool

yum install perl-Image-ExifTool

Fedora Commons

See the installation instructions.

JHOVE

JHOVE (JSTOR/Harvard Object Validation Environment) – pronounced “jove” – is a joint project of JSTOR and the Harvard University Library to develop an extensible framework for format validation. JHOVE is a format-specific digital object validation API written in Java.

Obtaining JHOVE

Download JHOVE’s recent distribution from http://sourceforge.net/project/showfiles.php?group_id=221311. At the time of writing this guide, the recent distribution is version 1.4 and the direct download link is http://sourceforge.net/projects/jhove/files/jhove/JHOVE%201.4/jhove-1_4.tar.gz/download.
To download JHOVE v1.4, execute:

wget http://sourceforge.net/projects/jhove/files/jhove/JHOVE%201.4/jhove-1_4.tar.gz/download

Installing JHOVE

• Extract JHOVE tarball (jhove-*.tar.gz).

  tar -zxvf jhove-*.tar.gz

  This should extract the jhove tarball and create a directory called “jhove” at the current location.

• JHOVE installation base directory (the jhove directory that we have just created by extracting in the previous step), should be copied to “/usr/local/src/”.

cp -av jhove/ /usr/local/src/

Configuring JHOVE

• Download “jhoveConfig.xsd” file and place it to your apache’s DocumentRoot directory (i.e. /var/www/html/).

wget hul.harvard.edu/ois/xml/xsd/jhove/jhoveConfig.xsd
mv jhoveConfig.xsd /var/www/html/
chmod 755 /var/www/html/jhoveConfig.xsd
chown apache:apache /var/www/html/jhoveConfig.xsd
chcon --reference=/var/www/html/ /var/www/html/jhoveConfig.xsd

• Change your directory to JHOVE’s installation directory.

  cd /usr/local/src/jhove/

• Edit the JHOVE’s configuration file. Open the file “conf/jhove.conf” in a file editor.

  vim conf/jhove.conf

• Replace the line “<jhoveHome>/users/stephen/projects/jhove</jhoveHome>” with “<jhoveHome>/usr/local/src/jhove/</jhoveHome>”.
• Replace the line “<tempDirectory>/var/tmp</tempDirectory>” with “<tempDirectory>/tmp</tempDirectory>”.
• Replace the line xsi:schemaLocation=”http://hul.harvard.edu/ois/xml/ns/jhove/jhoveConfig
  http://hul.harvard.edu/ois/xml/xsd/jhove/1.4/jhoveConfig.xsd”> with xsi:schemaLocation=”http://hul.harvard.edu/ois/xml/ns/jhove/jhoveConfig http://localhost/jhoveConfig.xsd”>
• Save the file and exit the editor.
• Edit the JHOVE’s shell script. Open the file “jhove” in a file editor.

  vim jhove

• Replace the line “JHOVE_HOME=[fill in path to jhove directory]“ with “JHOVE_HOME=/usr/local/src/jhove/”.
• Replace the line “JAVA_HOME=/usr/java” with “JAVA_HOME=/opt/jdk1.6.0_17/”. Note, we are assuming that we have installed Sun JDK at /opt/jdk1.6.0_17/. If you have a different location for Sun JDK installation, use the path of that directory in this step.
• Replace the line “${JAVA} -classpath $CP Jhove $ARGS” with “${JAVA} -classpath $CP Jhove -c ${JHOVE_HOME}/conf/jhove.conf $ARGS”.
• Save the file and exit the editor.
• Set proper file permissions.

chmod -R 755 /usr/local/src/jhove/

• Change your directory to /usr/local/.

  cd /usr/local/

• Make a symbolic link to the jhove installation directory here.

  ln -s /usr/local/src/jhove/

Prepare Environment Variables

• JHOVE_HOME: This variable should point out to the jhove installation base directory.
• PATH: This variable should include the path to the jhove installation base directory so that the jhove script could be run without pointing out the absolute path.

To prepare these variables we would add the instruction in the file /etc/profile.d/fedora-profile.sh. Remember that we have used the same file while installing and configuring fedora.

• Edit the file /etc/profile.d/fedora-profile.sh. Open the file in an editor.

  vim /etc/profile.d/fedora-profile.sh

• Add/Edit these lines:

JHOVE_HOME=/usr/local/src/jhove
PATH="$PATH:$FEDORA_HOME/server/bin:$FEDORA_HOME/client/bin:/usr/local/src/jhove"
export JHOVE_HOME PATH

Remember not to delete other lines in the file. Also the last statement should include other variables like CLASSPATH JAVA_HOME etc.

• Save the file and exit the editor.

Configure MySQL

• Edit /etc/my.cnf and add the following in the [mysqld] section:

# Fez customization
ft_min_word_len=2

• Check is MySQl service is running:

service mysqld status

• If it is not running, start it:

service mysqld start

• If MySQL service is already running, you need to restart the service:

service mysqld restart

• To make mysql run at every startup:

chkconfig mysqld on

• Login to MySQL.

mysql -u root -p

Type the password for the MySQL root user and press [Enter].

• Create a database for fez. At the mysql prompt, execute:

CREATE DATABASE fez default charset utf8;

• Create a user for fez and assign all privileges to the user on the fez database.

GRANT ALL ON fez.* TO fezuser@localhost IDENTIFIED BY 'userfez';
FLUSH privileges;

Note: Use your own password instead of “userfez”.

• Exit MySQL prompt.

Obtaining Fez

You can download the installation bundle of Fez at Fez’s page at Sourceforge – http://sourceforge.net/projects/fez/. The recent bundle at the time of writing this guide is version 2.1RC3. The direct link to the download of version 2.1RC3 is http://sourceforge.net/projects/fez/files/Fez/Fez%202.1%20RC3/fez-2.1_rc3.tar.gz/download.
To download the 2.1RC3 bundle, execute:

wget http://sourceforge.net/projects/fez/files/Fez/Fez%202.1%20RC3/fez-2.1_rc3.tar.gz/download

Installing Fez

• Extract the Fez installation tarball (fez-*.tar.gz).

tar -zxvf fez-*.tar.gz

This should create a directory call fez-2.1_rc3 (if you are using version 2.1RC3).

• Move the Fez directory to Apache’s DocumentRoot (i.e. /var/www/html/).

mv fez-2.1_rc3/ /var/www/html/fez/

Note: Here we are renaming the directory to “fez” while moving.

• Create a file called error_handler.log inside the fez installation directory.

touch /var/www/html/fez/error_handler.log

• Create an “incoming” directory inside fez installation directory.

mkdir -p /var/www/html/fez/incoming/

• Create an “duplicates_reports” directory inside fez installation directory.

mkdir -p /var/www/html/fez/duplicates_reports/

• Change permissions on the directory.

chmod -R 755 /var/www/html/fez/
chown -R apache:apache /var/www/html/fez/
chcon -R --reference=/var/www/html /var/www/html/fez/

• Start/Restart Apache service.

Note: Ensure that proper SELinux settings are made or SELinux is set into permissive mode, else the page would not be displayed, and you will get a Apache’s permission error page.

• Open a browser and point at http://localhost/fez/. This should open the fez installation page. Click on the “Proceed to the first step” button.
• The next page would ask you about “Core Settings”.
• Keep the “Application path” at “/var/www/html/fez/” which is also the default option.
• Set the “Relative path” to “/fez/”.
• Choose “Database type” as “MySQL”.
• Set “Database host” to “localhost”.
• Set “Database name” to “fez”. Remember to use a different name if you have created a different database for fez in the section “Configuring MySQL”.
• Set “Database username” to “fezuser”.
• Set “Database password” to “userfez”.
• Click on “Proceed to next step” button.
• At this step you shall see an alert box saying “Please allow a couple of minutes for the next step to be performed. Do not refresh the next page during this time.”. Click on the “OK” button.
• The next stage/page will show you if your installation was successful or not. Typically, the first line on the page should say “Success!”. If the installation was successful, you need to delete the setup directory.

rm -Rf /var/www/html/fez/setup/

Configuring Apache for Fez

• Create a apache configuration file for fez.

touch /etc/httpd/conf.d/fez.conf

• Edit the configuration file.

vim /etc/httpd/conf.d/fez.conf

• Add the following lines to the file:

Alias /fez /var/www/html/fez/

<Directory "/var/www/html/fez/">
	Options Indexes FollowSymLinks
	AllowOverride All
	Order Allow,Deny
	Allow from All
</Directory>

• Save the file and exit the editor.
• Open php.ini to tweak a few settings.

vim /etc/php.ini

• Set upload_max_filesize to 10MB. This sets the limit of the maximum file size for upload to be 10 MB rather than the default 2MB.

upload_max_filesize = 10M

• Set post_max_filesize to 10MB.

post_max_size = 10M

• Save file and exit the editor.
• Restart Apache (httpd service).

Configuring Fez

• Ensure Fedora service is running.
• Point your browser to http://localhost/fez/. If your browser shows you a lot of warnings related to PHP saying “Warning: Call-time pass-by-reference has been deprecated …”, this means that the version of PHP you are running on your machine has deprecated one of the feature called “Call-time pass-by-reference” and you need to make some changes to stop the warning from being displayed. You need to set the “error_reporting” to “E_ERROR”. To change the error reporting level:

sed -i -e 's/E_ALL ^ E_NOTICE/E_ERROR/' /var/www/html/fez/config.inc.php

Now refresh the fez startup page, it should not show you that error again.

• Click on the login link to open the login page. Use these credentials (the default username and password) to log in:

username: admin
password: admin

• After successfully logging in, you should see the “Administration” link in the top left corner of the page. Click on the link.
• Now you are directed to the Configuration page where you can see a lot of configuration options. On the left pane, click on the “Site Configuration” link. This should open the site configuration settings on the right pane.
• Click on the “General Settings” link.
• Set the “Application Name” to an appropriate name like “Pustakalaya”.
• Set the “Admin Email” to a valid email address.
• Set the “Organization Name” to an appropriate name.
• Set the “Short org. Name” to the short form of the organization’s name.
• Set the “Hostname” to “localhost” if you are testing fez, else set it to an appropriate DNS resolvable hostname, or the IP address.
• Set the “SMTP Server” to an appropriate SMTP server’s address(name or IP) which the application should use while sending emails.
• Set the “System email from address” to an appropriate and valid email address. Fez will use that address as a value for the field “FROM” email address while sending mails.
• Set other options as per your choice.
• Click on the “Save Changes” button.
• Next, click on the “Fedora Settings” link. Remember, much of the settings come from the previous stage where we installed Fedora Commons. Refer to those settings.
• Set “Version” to 2.2 or 2.2.1, which is also the default option.
• Set “Location” to localhost:8080/fedora.
• Set “Server Setup” to no-ssl-authenticate-all.
• Set “PID namespace” to Pustakalaya or the PID Namespace that you have used which configuring Fedora.
• Set “Username” to the Fedora Commons username (i.e. fedoraAdmin).
• Set “Password” to Fedora Commons Password (i.e. adminFedora).
• Set “Database Name” to fedora22.
• Set “Database Username” to adminFedora.
• Set “Database password” to adminFedora.
• Click on the “Save Changes” button.
• Next, click on the “Programs and Paths” link.
• Set the “SAN import directory” to /var/www/html/fez/incoming/.
• Set “Duplicate reports directory” to /var/www/html/fez/duplicates_reports/.
• Set “Graphviz DOT executable location” to /usr/bin/dot.
• Set “PHP executable location” to /usr/bin/php.
• Click on the “Save Changes” button.

You can choose to configure other options as well. In this example installation we would not change other stuffs. After you are done with the configuration and saved them, Click on the “Sanity Checks” link. This shall open a new tab/window. It will check fez installation and report if there are any problems.
If the sanity test reports error like:

Failed:  ConnectHTTP  APP_BASE_FEDORA_APIM_DOMAIN   = 'http://fedoraAdmin:adminFedora@localhost:8080/fedora'  HTTP Result 401 code.

then you have to edit a file at /var/www/html/fez/includes/class.sanity_checks.php

• Open that file in a text editor.

vim /var/www/html/fez/includes/class.sanity_checks.php

• Replace SanityChecks::checkHTTPConnect(‘APP_BASE_FEDORA_APIM_DOMAIN’,APP_BASE_FEDORA_APIM_DOMAIN)); with SanityChecks::checkHTTPConnect(‘APP_BASE_FEDORA_APIM_DOMAIN’,APP_BASE_FEDORA_APIM_DOMAIN.’/'));.
• Exit the editor.

All the errors are self explanatory, read them carefully to find out problems with your installation and finally fix them.

Now you are ready to use a full fledged repository based online Library.

This guide is geared towards helping novice users setup Fedora Commons repository. This guide contains easy steps which helps users go through various steps without much hassle. The guide makes assumption that the user is running either Fedora Linux or a compatible GNU/Linux distribution (e.g. RHEL, CentOS). Even though, with a few changes, the installation can be performed under other Linux distributions. All the commands should be run as an authenticated user, either as “root” or with “sudo”.

Conventions

• [Square braces] are used to denote keystrokes.
• “Quotes” are used to denote values and keywords.

Introdution

Fedora (or Flexible Extensible Digital Object Repository Architecture) (not to be confused with the Linux distribution named Fedora) is a modular architecture built on the principle that interoperability and extensibility is best achieved by the integration of data, interfaces, and mechanisms (i.e., executable programs) as clearly defined modules. Fedora is a digital asset management (DAM) architecture, upon which many types of digital library, institutional repositories, digital archives, and digital libraries systems might be built. Fedora is the underlying architecture for a digital repository, and is not a complete management, indexing, discovery, and delivery application. (Source Wikipedia)

Install Prerequisites

Sun Java Development Kit (JDK)

1. Go to http://java.sun.com/javase/downloads/index.jsp and download the JDK (the current, at the time of writing, is JDK 1.6 update 17). Choose the *.bin version to download.
2. After downloading, as a root user execute:

   		sh jdk*.bin

3. It will display the End User License Agreement (EULA), which you have to scroll down (press [SPACE] key to scroll). At the end, it will ask you if you accept or deny the license, type yes at the prompt and press [Enter]. It will take a while it generates files and installs the JDK on your machine. After a few minutes, the installation shall open a browser window, close that window, and the installation will be complete.
4. This shall create a directory in the current location in the format jdk1.6.0.7_17. Copy the whole directory to /opt and set 755 permission on it.

   cp -a jdk1.6.0.7_17/ /opt/
   chmod -R 755 /opt/jdk1.6.0.7_17/

5. Next, you need to set Sun JDK as the default Java handler for your system. To install Sun’s JDK as the default, execute:

   alternatives --install /usr/bin/java java /opt/jdk1.6.0.7_17/bin/java 20000

6. You need to first check the list and verify if Sun JDK is listed as an option for java handler. To see the list, execute:

   alternatives --config java

   This shall display a list of all the programs that can handle Java. Additionally it also displays a prompt where you can select the program that you want to be default Java handler. Each program in the list is given a number, and at the selection prompt, you just have to type the respective number. Look for something like “/opt/jdk1.6.0_17/bin/java” in the list and type its corresponding number at the prompt and press [Enter].To check if Sun Java is the default handler, execute:

   java -version

   It shall display information like:

   java version "1.6.0_17"
   Java(TM) SE Runtime Environment (build 1.6.0_17-b08)
   Java HotSpot(TM) Server VM (build 17.0-b16, mixed mode)

   This means that Sun Java is installed and being used as default Java handler

MySQL Database Server

To install MySQL database server, we will use the yum tool. Execute at the terminal as a root user:

yum -y install mysql mysql-server mysql-connector-java mysql-connector-odbc mysql-libs

Install Servlet Container (Apache Tomcat Server)

Since we will be using the tomcat server included with fedora installation, we will NOT INSTALL a separate server. If you intend to use a separate server, execute the following command as root user at the terminal to install tomcat server:

yum -y install tomcat5 tomcat5-webapps tomcat5-admin-webapps

Obtain Fedora Commons Installer

Download Fedora commons installer from the sourceforge.net project page at http://downloads.sourceforge.net/fedora-commons/. If you are planning to integrate fedora with Fez (which is a front-end to Fedora Commons), you need to choose to download version 2.2.1. The direct link to download of version 2.2.1 is http://sourceforge.net/projects/fedora-commons/files/fedora/2.2.1/fedora-2.2.1-installer.jar/download.

Prepare Environment Variables

Although the environment variables are not strictly required during the time of installation, but they are required at the time of starting the fedora server. So it is always a safe point to set the environment variables before starting the installation. You need to set the following environment variables:

JAVA_HOME

This variable should point at the the base directory of Sun JDK installation. For this example it should be /opt/jdk1.6.0_17/.

FEDORA_HOME

This variable should point at the base directory of Fedora commons installation. For this example, we will use /var/opt/fedora/ for the installation base.

CATALINA_HOME

This variable should point at the base directory of the tomcat installation that is to be used with fedora commons. For this example we will use the bundled tomcat, so we will set this variable to “$FEDORA_HOME/tomcat” which means that that the tomcat base directory resides under the fedora installation directory. If you intend to use an existing tomcat, set this variable to the base directory of tomcat (e.g. “/usr/share/tomcat5″).

JAVA_OPTS

This variable should include additional arguments to be included to make fedora run efficiently. We set the following arguments:
* Djavax.net.ssl.trustStore: The truststore location for SSL sessions (if SSL is enabled)
* Djavax.net.ssl.trustStorePassword: The truststore password
* Xmx: Allocated memory

PATH

This variable should include the absolute path to the java and fedora bin directories. So we shall add/append /var/opt/fedora/client/bin and /opt/jdk1.6.0_17/bin to this variable.

CLASSPATH

This variable should point to the Java lib directory. So we shall set this variable to /opt/jdk1.6.0_17/jre/lib.

Now we shall create a shell script that sets these variables. The intention behind using a shell script is that it can be called any time (preferably during every fedora service start-up), so as to ensure that the environment variables are always set and point to right values. To create the script, follow these steps as a root user at the terminal:

cd /etc/profile.d/
touch fedora-profile.sh

Edit the file “fedora-profile.sh”. To edit use the vim command:

vim fedora-profile.sh

Add the following lines to the file:

FEDORA_HOME=/var/opt/fedora
JAVA_HOME=/opt/jdk1.6.0_17/
CLASSPATH=$JAVA_HOME/jre/lib
CATALINA_HOME=/var/opt/fedora/tomcat/
JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.trustStore=$FEDORA_HOME/server/truststore"
JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.trustStorePassword=tomcat"
JAVA_OPTS="$JAVA_OPTS -Xmx512m"
PATH="$PATH:$FEDORA_HOME/server/bin:$FEDORA_HOME/client/bin"
export JAVA_HOME CLASSPATH CATALINA_HOME JAVA_OPTS FEDORA_HOME PATH

Save the file and exit from the vim editor. Also set executable permission to the file:

chmod 755 fedora-profile.sh

Run the script to set the environment variables. Execute:

sh fedora-profile.sh
source /etc/profile.d/fedora-profile.sh

Prepare Database for Fedora Commons

Start MySQL server

Check if mysqld database server is running. Execute:

service mysqld status

If the database server is not started, start the service by executing:

service mysqld start

To make the mysqld service start at every startup, execute:

chkconfig mysqld on

Login to MySQL

To login to mysql as root user, execute:

mysql -u root -p

Provide the mysql’s root password, and press [Enter].

Create a database for Fedora Commons

Fedora 2.2 installation by default uses a database named “fedora22″. So we require to create that database. Execute, at the mysql prompt:

CREATE DATABASE fedora22 default charset utf8;

Add the database user and grant permissions on the database

In this example we create a user named “adminFedora” and the password “adminFedora” and give all permissions to the user on the fedora database (i.e. fedora22).

GRANT ALL ON fedora22.* TO adminFedora@localhost IDENTIFIED BY 'adminFedora';
FLUSH PRIVILEGES;

Quit from the mysql prompt.

Install Fedora Commons

• Move to the directory where you have downloaded the installation jar file (e.g. fedora-2.2.1-installer.jar).
• To start installation, execute:

  java -jar fedora-2.2.1-installer.jar

• This will start the installation, during which you shall be asked several questions. For the context of this example, we shall use the predefined values as answers, which can be changed as per your requirement/choice.
• The first question would be a choice between three different modes of installation (viz. quick, custom, client). In this example, since we are trying to install a fedora commons server having custom configurations, we will choose the “custom” mode. Type custom at the prompt and press [Enter].
• The next question you get is the location/path of the base directory of fedora installation. If you’ve already set the FEDORA_HOME environment variable, the installer will display you the default value. If the default value is displayed, and you want to choose the default value, press [Enter] without typing anything; else type the full absolute path of the installation directory (e.g, /var/opt/fedora) and press [Enter].
• The next question you encounter is the password required to administer the fedora installation. It is the password of the fedora Administrative user called “fedoraAdmin”. In this example we shall use the password “adminFedora”. Hence type adminFedora and press [Enter].
• The next question is the hostname of the fedora server. The default is “localhost”. In this example, we shall use the default value, and hence press [Enter] without typing any value at the prompt.
• Then you shall be asked about the Authentication requirement for API-A, for which we shall use the default value which is “false” and hence press [Enter].
• Next you shall be asked about SSL Availability. For this example, we will disable SSL support, hence we will type false at the prompt and press [Enter].
• The next step will ask you about how to setup the servlet engine. The available options are “included”, “existingTomcat”, “other”. The “included” option shall install the bundled tomcat into the $FEDORA_HOME directory, “existingTomcat” to use the tomcat installation that has previously been installed, “other” to use other servelet engines like “jetty”. For this example, we will choose the “included” tomcat which is the default option, and hence press [Enter] at the prompt.
• Next you shall be asked about the path for tomcat installation base directory. The default option is $FEDORA_HOME/tomcat (i.e. in our example /var/opt/fedora/tomcat), if you have chosen to install the “included” tomcat bundle. We shall choose the default option, and hence press [Enter] at the prompt. If the default installation base is not displayed, you’ll need to type the path manually and press [Enter].
• Next you shall be asked the Tomcat HTTP Port that is the default NON-SSL port for fedora (the port on which tomcat will listen to). The default option is port 8080. We shall choose the default option and hence press [Enter] at the prompt.
• Next you shall be asked the Tomcat Shutdown Port. The default option is 8005. We shall choose the default option, and hence press [Enter] at the prompt.
• Next you shall be asked about if the XACML policy should be enforced or not. The default option is “true”. We shall choose the default option, and hence press [Enter] at the prompt.

The next steps will take you to the database configuration.

• At this step, you shall be asked about the database provider to use. The available options are “mckoi”, “mysql”, “oracle”, “postgresql” and “included”. For this example we shall be using Fedora Commons with MySQL database, hence we will type mysql at the prompt and press [Enter].
• Next you shall be asked about the database driver (JDBC driver, since we are using java). You are required to type the full absolute path of the driver. Since we shall be using the “included” JDBC driver which is also the default option, and hence we press [Enter] at the prompt.
• Next you shall be asked about the database username that would be used to connect to the database. In the previous section entitled “Prepare Database for Fedora Commons” we had setup a user name with the credentials: Username – “adminFedora”, and Password – “adminFedora”. Hence we shall use the same credentials. If you have used a different username, you can supply it here. Type adminFedora at the prompt and press [Enter].
• Next you shall be asked about the database password to be used to acess the fedora database. The password should correspond to the user that we have entered in the previous step (in the example, the password of the “adminFedora” mysql user). In the example, the password is “adminFedora”. Type adminFedora at the prompt and press [Enter].
• Next you shall be asked about the jdbc url that would be used to connect to the database. The default option is “jdbc:mysql://localhost/fedora22?useUnicode=true&characterEncoding=UTF-8&autoReconnect=true”. You should replace “fedora22″ in the url with a appropriate database name, if in the previous section you have chosen to create a database (for fedora) with a different name rather than “fedora22″. We shall use the default option, and hence press [Enter] at the prompt.
• Next you shall be asked about the JDBC driver class. We shall use the default option and hence press [Enter] at the prompt.
  If the installer succeeds to connect to the database using the configuration values as supplied to it in the previous step, it will take you to the next configuration steps, else it will repeat the database configuration section.
• After succeeding to connect to the database, it will ask you if you want to deploy local services and demo. The demo objects are good for testing fedora installation. The default option is “true”. We shall use the default option, and hence press [Enter].
  It will take a while for the installer while it prepares the fedora base directory will all the essential files and directory structure, plus configuring the servlet engine and deploying local and demo applications. After performing these steps, the installer will quit giving you an clear notice that fedora have been installed and you must configure the required environment variables in order to run fedora.

Configure Fedora Server

Fedora Commons server comes with configuration file that can be changed to tweak its behaviour. The configuration file is located at “$FEDORA_HOME/server/config/fedora.fcfg” (i.e. “/var/opt/fedora/server/config/fedora.fcfg” in our example. In the example installation we shall only change a few configuration to make our task easier.

• Open the fedora.fcfg file in editor. Execute:

  vim $FEDORA_HOME/server/config/fedora.fcfg

• Edit the line <param name=”adminEmailList” value=”bob@example.org sally@example.org”>, in the value part type the email address(es) of the Fedora Commons administrator. If you want to keep more than one email address, separate the entries with a space.
• Edit the line <param name=”ENFORCE-MODE” value=”enforce-policies”/> and in the value part replace “enforce-policies” with “permit-all-requests”.
• Edit the line <param name=”pidNamespace” value=”changeme”>, in the value part, replace “changeme” with the required pidNamespace. In this example, we shall use the pidNamespace as “Pustakalaya”.
• Edit the line <param name=”retainPIDs” value=”demo test changeme fedora-bdef fedora-bmech tutorial”> and replace “changeme” with the pidNamespace that we have chosen in the previous step. In the example, we shall replace “changeme” with “Pustakalaya”.
• Save the file and exit the editor.

Configure the Tomcat Servlet Engine

The configuration of the tomcat servlet engine is located in a file at $CATALINA_HOME/conf/server.xml (i.e. /var/opt/fedora/tomcat/conf/server.xml in our example installation). The default configuration is well appropriate to run, but we will change a few settings to make our work easier.

• Open the server.xml file in a editor. Execute:

  vim $CATALINA_HOME/conf/server.xml

• Edit the line <Connector port=”8080″ maxThreads=”150″ minSpareThreads=”25″ maxSpareThreads=”75″ enableLookups=”true” redirectPort=”8443″ acceptCount=”100″ debug=”0″ connectionTimeout=”20000″ disableUploadTimeout=”true”/> and replace enableLookups=”true” with enableLookups=”false”.
• Save the file and exit the editor.

Set Fedora Commons as a service

This setup is optional, but is recommended since it shall make things easier. In this step we will create a shell script that will interact with the standard “service” command, and helps us to start, stop, check status, reload fedora commons server. To create the script, follow these steps:

• Create the service script. Execute:

  touch /etc/init.d/fedora

• Edit the file in the editor. Execute:

  vim /etc/init.d/fedora

• Add these lines in the file:

  #!/bin/sh
  #
  # fedora commons database
  #
  # chkconfig:   - 20 80
  # description: Fedora commons content library
  
  ### BEGIN INIT INFO
  # Provides: fedora
  # Required-Start: mysqld
  # Required-Stop: mysqld
  # Short-Description: Fedora commons content library
  # Description: Fedora commons content library
  ### END INIT INFO
  
  . /etc/rc.d/init.d/functions
  . /etc/profile.d/fedora-profile.sh
  
  export CATALINA_PID=/tmp/fedora-catalina.pid
  
  # determines if Fedora is running by examining the command line of a certain
  # pid.
  # args: <suspected pid of Fedora>
  fedora_alive()
  {
  #echo $1
  [ -d /proc/"$1" ] || return 1
  cmd=$(ps -p "$1" -o command=)
  [ $? == 0 ] || return 1
  [[ "${cmd}" =~ ".*java.*fedora.*tomcat.* start$" ]]
  echo $?
  }
  
  status()
  {
  [ -e "$CATALINA_PID" ] || return 3
  local pid=$(<$CATALINA_PID)
  #fedora_alive $pid || return 3
  #echo "Fedora running at pid $pid"
  fedora_alive $pid && rt=0 || rt=3
  if [ $rt -eq 0 ]
  then
  echo "Fedora Commons service is running at pid $pid"
  else
  echo "Fedora Commons service is stopped."
  fi
  return $rt
  }
  
  start()
  {
  local pid=""
  [ -e $CATALINA_PID ] && pid=$(<$CATALINA_PID)
  if [ -n "$pid" ] && fedora_alive $pid; then
  echo "Fedora Commons service already running as pid $pid"
  return 1
  fi
  
  # reset working directory, because the java process takes a handle on
  # the directory from where this init script was ran
  cd /
  
  /var/opt/fedora/tomcat/bin/startup.sh > /dev/null
  if [ $? -eq 0 ]
  then
  action "Starting Fedora Commons Service: " /bin/true
  else
  action "Starting Fedora Commons Service: " /bin/false
  fi
  }
  
  stop()
  {
  local pid=$(<$CATALINA_PID)
  /var/opt/fedora/tomcat/bin/shutdown.sh > /dev/null 2>&1
  retval=$?
  if [ $retval -eq 0 ]
  then
  action "Stopping Fedora Commons Service: " /bin/true
  else
  action "Stopping Fedora Commons Service: " /bin/false
  fi
  sleep 3
  [ -z "${pid}" ] && return $?
  
  for i in $(seq 0 10); do
  fedora_alive $pid || return 0
  
  echo "Fedora shutdown failed, retry in 5 secs"
  sleep 5
  /var/opt/fedora/tomcat/bin/shutdown.sh > /dev/null 2>&1
  done
  fedora_alive $pid || return 0
  echo "Force kill Fedora."
  kill ${pid}
  sleep 5
  fedora_alive || return 0
  kill -9 ${pid}
  }
  
  case "$1" in
  start) start ;;
  stop) stop ;;
  restart) stop; start ;;
  status) status ;;
  *)
  echo $"Usage: $0 {start|stop|status|restart}"
  exit 2
  esac
  exit $?

• Save the file and exit editor.
• Set proper permissions.

chmod 755 /etc/init.d/fedora

Start fedora service

To start the fedora service, you can now execute:

service fedora start

Test Fedora Commons

Test if MySQL Service is running

service mysqld status

Start the service if it has not yet started by executing:

service mysqld start

Test if Fedora Commons is running

service fedora status

Start the service if it is not yet started by executing:

service fedora start

You can also set the Fedora Commons service to automatically start at startup. Execute:

chkconfig --add fedora
chkconfig fedora on

Test tomcat servlet engine

Open a browser and browse http://localhost:8080. If the page displays Apache Tomcat Start page, this means the tomcat servlet engine is running.
Now browse to http://localhost:8080/fedora. It shall ask you the login credentials. Provide user-name as fedoraAdmin and password as adminFedora. Remember to use the password that we have supplied during the section “Install Fedora Commons”. After logging in, you shall see the “Apache-AXIS” page. This means that the fedora service is running well.

Further test with demo objects

This step is optional, but can be performed to see if fedora commons is behaving appropriately by storing objects, datastreams, and their metadata, as well as to check if it provides interface to retrieve and update those objects. To do this, we need to ingest the demo objects to the fedora server. Follow these steps:

• Ensure that all the required services and daemons and running.
• Open a terminal and follow these steps:

  cd $FEDORA_HOME/client/bin/
  fedora-ingest-demos.sh localhost 8080 fedoraAdmin fedoraAdmin http

• This step will ingest the demo objects to the fedora commons repository. To check the demo objects, open a browser and browse http://localhost:8080/fedora/get/demo:5. If it displays the page with the description of the demo object, this means that fedora is working correctly.
• The repository objects can be tested with the fedora GUI client as well.
• Open a terminal and follow these steps:

cd $FEDORA_HOME/client/bin/
./fedora-admin.sh

Type the password for the user fedoraAdmin, i.e. adminFedora in our example. Now you can use the UI for searching of objects, adding new objects to the repository and other actions.

Enjoy using the Fedora Commons data repository.

Redmine is an open source, web-based project management and bug-tracking tool. It includes calendar and gantt charts to aid visual representation of projects and their deadlines. It supports multiple projects. Redmine is a FOSS solution which provides integrated project management features, issue tracking, and support for multiple version control options. Projects investigating commercial tools like IBM Rational Team Concert but wanting to stick with a FOSS solution may find this tool to be a good starting point though without the full depth and breadth of commercial SCRUMM and AGILE tools.
The design of Redmine is significantly influenced by Trac, a software package with some similar features. Redmine is written using the Ruby on Rails framework. It is cross-platform and cross-database.(Source: Wikipedia)

Prerequisites

• Ruby
• Gem
• Rails
• Ruby Development Libraries
• Ruby Sqlite support
• Thin
• Apache webserver with proxy modules
• MySQL

To install the prerequisites, you can issue theses following commands at the terminal as a root user:

yum -y groupinstall"Web Server" "Ruby"
yum -y install rubygem-rails rubygem-sqlite3-ruby ruby-devel mysql mysql-libs mysql-server ruby-mysql ImageMagick ImageMagick-devel

Obtaining Redmine

Redmine is a free software and you can obtain redmine from this link: http://rubyforge.org/frs/?group_id=1850. Please, select the recent bundle to download.

Pre-Installation Tasks

Updating the GEM system

gem update --system

Setup Thin

gem install rack rmagick thin
thin install

Configure Thin for your server

chkconfig --add thin
chkconfig --level 345 thin on

Configuring Apache as a load balancer and proxy

Edit /etc/httpd/conf/httpd.conf file and put these lines if they are already not there:

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
<IfModule mod_proxy.c>
       #turning ProxyRequests on and allowing proxying from all may allow
       #spammers to use your proxy to send email.
       ProxyRequests On
       <Proxy *>
                AddDefaultCharset off
                Order deny,allow
                Allow from 127.0.0.0/255.0.0.0
       </Proxy>
       # Enable/disable the handling of HTTP/1.1 "Via:" headers.
       # ("Full" adds the server version; "Block" removes all outgoing Via: headers)
       # Set to one of: Off | On | Full | Block
       ProxyVia On
</IfModule>

Configure Thin for your application

Create a thin configuration file for your application:

thin config -C /etc/thin/<config-name>.yml -c <rails-app-root-path> --servers <number-of-threads> -e <environment>

Replace <config-name> with the name of the configuration file, <rails-app-root-path> with the path to the root of your application, <number-of-threads> with the number of Thin processes to be started and <environment> with the environment in which to run the code. For example:

Since our example setting contains:

<application-name> = myredmineapp
<rails-app-root-path> = /var/redmine
<number-of-threads> = 3
<environment> = production

the following code will set that for us:

thin config -C /etc/thin/myredmineapp.yml -c /var/redmine --servers 3 -e production

Adding an Apache virtual host for Redmine

Now you can create a virtual host to host your Redmine application.

• Add a configuration file in the conf.d directory of your httpd base (i.e. /etc/httpd/conf.d):

touch /etc/httpd/conf.d/redmine

• Open the file to add content.

vim /etc/httpd/conf.d/redmine

• Add the virtual host configuration to the file.

<VirtualHost *>
        ServerName redmine.yourdomain.com
        DocumentRoot /var/redmine
        <Proxy balancer://mycluster>
                 BalancerMember http://127.0.0.1:3000
                 BalancerMember http://127.0.0.1:3001
                 BalancerMember http://127.0.0.1:3002
        </Proxy>
        ProxyPass / balancer://mycluster/
        ProxyPassReverse / balancer://mycluster/
        ErrorLog /var/log/httpd/error.log
        CustomLog /var/log/httpd/access.log vcombined
        CustomLog /var/log/httpd/redmine-access.log combined
</VirtualHost>

Change “redmine.yourdomain.com” with a virtual host of your setting.

• Save the file and exit the editor.

Redmine Installation

Setting the Redmine Installation base

• Move to the directory containing Redmine tarball.
• Extract the tarball to the parent directory of Redmine installation (i.e. in our case /var/).

tar -xvf redmine-*.tar -C /var/
mv /var/redmine-* /var/redmine/

• Set permission to read and execute to the public directory.

chmod -R a+rx /var/redmine/public/
cd /var/redmine/
chmod -R 755 files log tmp public/plugin_assets

Database Configuration

• Create the database configuration file.

cd /var/redmine/config/
cp database.yml-example database.yml

• Edit the database.yml file and delete all the lines expect for the production section. Tweak the parameters of the production section to fit your settings:

vim /var/redmine/config/database.yml

production:
	adapter: mysql
	database: redmine
	host: localhost
	username: redmine
	password: <redmine_mysql_password>
	socket: /var/lib/mysql/mysql.sock

Change <redmine_mysql_password> with a valid password string and remember the same password will be used which configuring the database.

• Start services.

service httpd start
service mysqld start
service thin start

• Create the database and user for Redmine.

mysql -u root -p

When asked, provide the password for the MySQL's root user.

create database redmine default character set utf8;
grant all on redmine.* to redmine@localhost identified by '<redmine_mysql_password>';
flush privileges;

• Generate a session store secret.

cd /var/redmine/
RAILS_ENV=production rake config/initializers/session_store.rb

• Run Database object creation script:

cd /var/redmine/
RAILS_ENV=production rake db:migrate

Final Touch

• Restart thin service.

service thin restart

• Set Apache and MySQL to run at startup.

chkconfig mysqld on
chkconfig httpd on

Now you can browse you site at either at http://localhost:3000 or at http://redmine.yourdomain.com .

Introduction

Bugzilla is a web-based general-purpose bug tracker and testing tool originally developed and used by the Mozilla project, and licensed under the Mozilla Public License. Released as open source software by Netscape Communications in 1998, it has been adopted by a variety of organizations for use as a defect tracker for both free software and proprietary products. (Source: Wikipedia)

Prerequisites

• Perl (5.8.1 or above)
• Database Engine (MySQL or Oracle or PostgreSQL)
• Webserver (Apache, IIS)
• Required Perl Modules
• Mail Transfer Agent (Sendmail 8.7 or above)

In this tutorial, we will be using a Fedora system with MySQL as the database server, apache as the webserver and Sendmail as the MTA. To install all of these prerequisites, you can issue the following command on the terminal as a root user:

yum -y install perl httpd sendmail mod_perl mysql mysql-server mysql-libs mysql-connector-odbc mysqlclient* perl-Class-DBI-mysql libcgi perl-DateManip perl-DateTime-Format-Builder libdbi libdbi-dbd-MySQL libdbi-drivers libdbi-devel perl-CGI-Untaint-email perl-CPAN perl-libxml-perl 

Obtaining Bugzilla

Bugzilla is a free software and you can download it from Bugzilla website. To download the recent stable release, follow this link.

Installation of Prerequisites

• Be sure you’ve installed all the prerequisites as discussed above.
• Download the Bugzilla recent stable release tarball.
• Copy the tarball to the httpd’s DocumentRoot (i.e. /var/www/html/):

cp bugzilla-*.*.*.tar.gz /var/www/html/

• Extract the tarball:

cd /var/www/html/
tar -zxvf bugzilla-*.*.*.tar.gz

• The previous command shall create a folder named bugzilla-*.*. Now, you can safely remove the tarball.

rm bugzilla-*.*.*.tar.gz

• Now we need to check the installed Perl modules and find a list of all the Perl modules to be installed.

cd bugzilla-*.*
./checksetup.pl --check-modules

• Next step is to install the required Perl modules (this assumes that you have CPAN installed in your computer). The following command will use CPAN LWP agent and install all the required modules.

perl install-module.pl --all

Configuration

After the installation of all the prerequisites has successfully been done, we configure and tune the installation.

• Move inside the bugzilla directory (/var/www/bugzilla-*.*) if you are not already inside it

cd /var/www/html/bugzilla-*.*

• Now run the check setup perl script to begin configuration.

./checksetup.pl

This time, checksetup.pl should tell you that all the correct modules are installed and will display a message about, and write out a file called, localconfig. This file contains the default settings for a number of Bugzilla parameters.

Load this file in your editor. The only two values you need to change are $db_driver and $db_pass, respectively the type of the database and the password for the user you will create for your database. Pick a strong password (for simplicity, it should not contain single quote characters) and put it here. $db_driver can be either ‘MySQL’, ‘Pg’ or ‘oracle’. Since we are using MySQL, the $db_driver variable should be set to ‘MySQL’.

• Set the $db_driver variable to ‘MySQL’.

$db_driver = 'mysql';

• Set $db_host to the hostname or ip of the myql server. The preferred value is ‘localhost’, since the same machine is also to be configured as a database server.

$db_host = 'localhost';

• Set the $db_name as ‘bugs’ and $db_user as ‘bugs’.

$db_name = 'bugs';
$db_user = 'bugs';

• Set $db_pass to the password of the ‘bugs’ database user in MySQL. Let’s assume that password is bugs123#.

$db_pass = 'bugs123#';

Note: You are encouraged to use your own strong password. This password has just been used as a reference. Remember, the same password needs to be used while creating a MySQL user for Bugzilla.

• After setting all the above variables, just save the file and exit the editor.
• Now we need to tune and configure MySQL to allow easy access to Bugzilla and its components. To do so edit the MySQL configuration file (generally /etc/my.cnfon Linux systems) and follow the following procedure:
  • Under the [mysqld] section inside that file, add directive to allow MySQL insert data bigger than 64K (default), since Bugzilla needs to insert data more than the default size. Bugzilla needs to use large attachments.

[mysqld]
# Allow packets up to 4MB
max_allowed_packet=4M

• Also, Bugzilla requires small words to be indexed in full-text search which is not enabled by default. Hence we need to add a directive to allow indexing of even small words in full-text search.

[mysqld]
# Allow small words in full-text indexes
ft_min_word_len=2

Rebuilding the indexes can be done based on documentation found at http://www.MySQL.com/doc/en/Fulltext_Fine-tuning.html.

• Now we add a database user defined by the variable $db_user (i.e. bugs) and set the password to $db_pass (i.e. bugs123#), though you are encouraged to use your own password. Further we set this user to have all sort of privileges over the $db_name (i.e. bugs) database.

GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES, CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY 'bugs123#';
FLUSH PRIVILEGES;

Note: Please use the same password that you specified in the localconfig file identified by the variable $db_pass.

• Next we allow MySQL to have attachment tables to grow beyond 4 GB (the default maximum limit is just 4 GB and Bugzilla might require more space). Although this step forms a part of database configuration, we will postpone this step until the rest part of the configuration is complete.

use bugs;
ALTER TABLE attachments AVG_ROW_LENGTH=1000000, MAX_ROWS=20000;

This command sets MySQL to let the attachment table grow up to 20 GB.

• Now after the local configuration file (i.e. localconfig) has been edited and all the other necessary configuration has been made, we again rerun the script to make Bugzilla bind to the configuration and create necessary files and setting parameters. Running the script reconfirms that all the modules are present, and notices the altered localconfig file, which it assumes you have edited to your satisfaction. It compiles the UI templates, connects to the database using the ‘bugs’ user you created and the password you defined, and creates the ‘bugs’ database and the tables therein. After that, it asks for details of an administrator account. Bugzilla can have multiple administrators – you can create more later – but it needs one to start off with. Enter the email address of an administrator, his or her full name, and a suitable Bugzilla password.

./checksetup.pl

• Next comes the configuration of the web-server to correctly display the Bugzilla pages and apply appropriate permissions to the Bugzilla installation base directory. Since we are using Apache web-server, we have two options to run Bugzilla. Bugzilla is written using Perl CGI, and hence two apache modules are available to run and show CGI scripts. You can choose any one of them (remember to install the required apache module before performing this step). Using mod_cgi is preferred.
  • Apache httpd with mod_cgi
    • Open the httpd configuration file (/etc/httpd/conf/httpd.conf).
    • Now we add a <directory> directive to the configuration file to permit fine-grained permission setting over the Bugzilla installation base.

Alias /bugzilla/ /var/www/html/bugzilla-*.*/

<Directory "/var/www/html/bugzilla-*.*">
	AddHandler cgi-script cgi
	DirectoryIndex index.cgi
	Options +Indexes +ExecCGI -MultiViews +SymLinksIfOwnerMatch +FollowSymLinks
	AllowOverride None
	Order allow,deny
	Allow from all
</Directory>

<Directory "/var/www/html/bugzilla-*.*/data">
	Options FollowSymLinks
	AllowOverride None
	Order allow,deny
	Allow from all
</Directory> 

• Save the configuration file and exit the editor.
• Run the checksetup.pl script to complete the configuration.

• Apache httpd with mod_perl
• Open the httpd configuration file (/etc/httpd/conf/httpd.conf).
• Add the following directive in the http configuration file before any other mod_perl directives:

PerlSwitches -I/var/www/html/bugzilla -w -T
PerlConfigRequire /var/www/html/bugzilla/mod_perl.pl

• Save the file and exit the editor.
• Run the checksetup.pl script to complete the configuration.
• Now restart the httpd daemon to apply the settings.

/sbin/service httpd restart

• Now, you can point your browser at http://localhost/bugzilla/ to open the Bugzilla page.
• At this point, you are required to login with the administrator account which you created while running the checksetup.pl script. Generally the user name is the email address that you provided while running the script.
• After logging in to the Bugzilla system, you are required to edit some key parameters. To edit the parameters, follow the “Administration” link on the top navigation bar, and from the page that opens, you can follow the “Parameters” link. Alternatively, you can point your browser to http://localhost/bugzilla/editparams.cgi.
  • Set the maintainer parameter to your email address <yourname@yourdomain.tld>.
  • Set the urlbase parameter to http://<hostname>/bugzilla/. Remember to replace the <hostname> with the appropriate hostname of the bugzilla server machine and don’t use “localhost” for this parameter.
  • Save the parameters by clicking on the “Save Changes” button at the bottom of the page.
• On the Parameters page, there is a vertical navigation bar on the left most part. The navigation bar contains links to various settings that you might want to change according to your need. After editing any of the parameters, don’t forget to save the changes. Unless the changes are saved, they are not applied to the Bugzilla system.
• Next you need to add products, components, versions, and milestones. For this purpose follow the “Administration” link on the top navigation bar and then follow the appropriate links. By default a test product and a test component is already added. You can edit those and replace by your own. The administration page also contains other link to other settings, you can choose to change them according to your need.
• From the administration page, follow the “Users” link and add new user and/or edit existing users.
• To change the preferences of the currently logged in user, follow the “Preferences” link at the bottom or top navigation bar, alternatively, you can point your browser to http://localhost/bugzilla/userprefs.cgi.
• You can file a new bug by following the “New” link on the navigation bar, alternatively you can point your browser to http://localhost/bugzilla/enter_bug.cgi.
• You can use the “Search” or the “Reports” features to get information about the bugs that have been filed by various users of the system.

Enjoy a robust bugtracker and testing platform.

SSH (SSH client) is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin and rsh, and provide secure encrypted communications between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP ports can also be forwarded over the secure channel. SSH connects and logs into the specified hostname (with optional user name). The user must prove his/her identity to the remote machine using one of several methods depending on the protocol version used. In this guide we will see how to set up a password-less method to authenticate to a SSH server.

Case Scenario

For this case, we make the following assumptions:

1. The originating host, which we would like to authenticate to a SSH server, is named “bob”.
2. The SSH server or the remote host is named “monica”.
3. Both machines have SSH package installed. Also that bob is equipped with SSH client and monica is equipped with OpenSSH server; and the server daemon is running on the default port (i.e. 22).
4. The user account on monica to which we want to authenticate is “foo” and the current logged in user on the bob’s machine is “bar”. Please replace “foo” and “bar” with actual user names; and “bob;” and “monica” with actual names of the machine in a real world.

Setting up the Authentication

Generating the key

• You need to generate a SSH key for your host if you have not yet generated. To generate a key, login to bob as the user “bar”. Run the following command:

ssh-keygen

• Now that you’re required to copy the key over the SSH server “monica”. To copy the file, we will use a tool called “SCP”. Follow these steps:

		cd ~/.ssh/ scp id_rsa.pub foo@monica:~foo/.ssh/bob_id_rsa.pub
		

Enabling authorization

Now that you need to add the SSH key from the file bob_id_rsa.pub to the file authorized_keys which resides under ~foo/.ssh/ directory. If the file does not exist, you have to manually create it.

1. Login to monica (the SSH server).

   				ssh monica -l foo
   				

2. Move to the .ssh directory.

   				cd ~/.ssh/
   				

3. Create the authorized_keys file (only if it does not exist).

   touch authorized_keys

4. Append bob’s SSH key to the key-file.

    cat bob_id_rsa.pub >> authorized_keys
    

   Remember to use double redirection (>>). If you use a single redirection (>), it will truncate the file and then add the SSH key from bob; all the other

5. Make sure that the files in .ssh are writable only by you, on both machines, and non-executable by anyone.

   				chmod 644 authorized_keys
   				

6. Exit from the monica’s SSH session.

   				exit
   				

Testing the setup

Try logging in to monica again.

ssh monica -l foo

Now you can notice that you don’t require a password to login.