• domain_name1.com: Your domain name
• extra_domain_name.com: Extra domains if your also using extra domain mapping in wordpress
• file_root: Path to your wordpress install

Files

/etc/nginx/sites-available/domain_name1.com

# WordPress Multi Site Domain
server {
    listen 80 ;
    server_name .domain_name1.com .extra_domain_name.com;

    root /file_root/wordpress;
    index index.php index.html index.htm;

    # Rewrite for multi site files
    rewrite /files/(.+)$ /wp-includes/ms-files.php?file=$1 last;

    # Rewrite for wordpress
    if (!-e $request_filename) {
        rewrite ^(.+)$ /index.php?q=$1 last;
    }

    location ~ \.php$ {
        fastcgi_pass    unix:/tmp/php-fastcgi.socket; # or port like 127.0.0.1:9000
        fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include         fastcgi_params;
    }
}

Finish

sudo ln -s /etc/nginx/sites-available/domain_name.com /etc/nginx/sites-enabled/domain_name.com
sudo service nginx restart

This is intended for situations where redmine needs to be served in a subdirectory via a nginx that is also used for other serving needs.

Some basic prerequisite knowledge of nginx and redmine will likely be needed.

Instructions are tested on redmine-svn and Ubuntu-9.10.

• Install dependencies

  • sudo apt-get install subversion libmysql-ruby rake rubygems mongrel nginx

• Setup directory structure

  • sudo adduser --system --group redmine
    sudo mkdir /opt/redmine
    sudo chown redmine:redmine /opt/redmine
    sudo -Hu redmine svn checkout http://redmine.rubyforge.org/svn/trunk /opt/redmine

• Create the MySQL database for redmine
  • Example for mysql-server on localhost:

    sudo apt-get install mysql-server
    mysql -u root -p
    create user 'redmine'@'localhost' identified by 'password';
    grant all privileges on  `redmine_%` . * to  'redmine'@'localhost';
    create database redmine_production character set utf8;
    quit;

  • (or use phpmyadmin)
• Copy config/database.yml.example to config/database.yml and edit the database configuration

  • sudo -Hu redmine cp /opt/redmine/config/database.yml.example /opt/redmine/config/database.yml
    sudo -Hu redmine vim /opt/redmine/config/database.yml

  • Example database spec:

    • production:
        adapter: mysql
        database: redmine_production
        host: localhost
        username: redmine
        password: password
        encoding: utf8

• Generate redmine session store secret

  • cd /opt/redmine
    sudo -Hu redmine gem install -v=2.3.5 rails
    sudo -Hu redmine rake generate_session_store

• Create the database structure and insert the default data

  • sudo -Hu redmine RAILS_ENV=production rake db:migrate
    sudo -Hu redmine RAILS_ENV=production rake redmine:load_default_data

• Setup redmine to be served from /redmine/

  • cd /opt/redmine/config
    sudo -Hu redmine cp additional_environment.rb.example additional_environment.rb
    echo 'config.action_controller.relative_url_root = "/redmine"' | sudo -Hu redmine tee -a additional_environment.rb

• Setup email delivery as desired

  • cd /opt/redmine/config
    sudo -Hu redmine cp email.yml.example email.yml

    • Example smtp spec

      • sudo -Hu redmine vim email.yml

        production:
          delivery_method: :smtp
          smtp_settings:
            address: smtp.example.com
            port: 25
            domain: example.com

• Start the mongrel server

  • cd /opt/redmine; sudo -Hu redmine mongrel_rails start -e production -p 9001 -d

• Edit /etc/nginx/sites-enabled/default

  • sudo vim /etc/nginx/sites-enabled/default

  • Add to the active server section:

    •         location /redmine {
                      alias /opt/redmine/public/;
                      try_files  $uri/index.html $uri.html $uri @mongrel;
              }
              location @mongrel {
                      proxy_set_header  X-Real-IP        $remote_addr;
                      proxy_set_header  X-Forwarded-For  $proxy_add_x_forwarded_for;
                      proxy_set_header  Host             $http_host;
                      proxy_redirect    off;
                      proxy_pass        http://127.0.0.1:9001;
              }

• Restart nginx:

  sudo service nginx restart

• Test the website. eg: http://localhost/redmine/
• If successful, set mongrel to start on boot

  • sudo vim /etc/rc.local

    • cd /opt/redmine; sudo -Hu redmine mongrel_rails start -e production -p 9001 -d

• Retest site after a reboot

I cannot remember what site I used as a reference when creating the diagram. The original was an ascii chart though. This is created in dia and exported to pdf too. Both attached for convenience. CC licensed as long as the original chart I copied allows it.

Packet flow examples:

All packets to or from localhost travel down the left side of the chart.

From external destination localhost: PREROUTING -> INPUT -> [Local Process] -> OUTPUT -> POSTROUTING.

From localhost destination external: OUTPUT -> POSTROUTING -> [External Host] -> PREROUTING -> INPUT.

All forwarded packets travel the right side of the chart and travel all three tables coming in and then again going out.

From external dest internal: PREROUTING -> FORWARD -> POSTROUTING.

Internal response to external: PREROUTING -> FORWARD -> POSTROUTING.

and so forth.

This is what caught me for a while. Forwarded packet travel the right side route and get out of (or in to) the network. The response then gets generated and does not start from FORWARD or POSTROUTING, but from PREROUTING again. So all NEW forwarded packets need to be marked in PREROUTING and the mark saved. Not new packets need that mark restored in PREROUTING, and all packets need that mark restored in POSTROUTING. (As demonstrated by my previous post).

Locally generated traffic only sees OUTPUT and POSTROUTING before hitting the network and needs to be marked before hitting POSTROUTING, hence the OUTPUT chain rules in my previous post.

I will accept changes to the chart too if anybody wants modifications made.

iptables routing.dia

iptables routing.pdf

http://www.cyrius.com/debian/orion/d-link/dns-323/install.html

The install took quite a while, I selected the standard package list. Then because it gets quit hot here in Griffith I really wanted to have fan control back, so instruction here were also followed.

As I wanted to install to an 8GB Flash drive I had handy I first uploaded the netboot.img firmware, turned off the DNS-323, removed the hard drives and left only the flash drive inserted, then powered up and followed the installation instructions.

I like keeping root on the flash drive as the hard drives can be stopped all day when not in use to save temp and power.

Fans are also controlled by lm-sensors and the unit seems to run about 47degC most of the day.

I use the unit mostly for irc (screen/weechat), rsync backup target and samba media server. It handles all that pretty well but I do notice it bog a fair bit with only 64mb ram and hard drive transfer rates are not as good as I am used to, but on the whole a great little unit (now that it runs debian).

Life Portal 5.2 Systems Development

• Author: Jonas X. Yuan
• Pages: 552
• Publisher: Packt Publishing
• Rating: 9/10
• ISBN: 1847194702
• Summary: A Java developer’s guide to developing custom intranet systems, based on Liferay’s platform

As one of only a few books on advanced Liferay Portal development Jonas had a LOT of material to cover. My two weeks of experience with Liferay up to this point had only involved deployment, configuration and theme development. After been impressed with the results so far my next three aims were customising the WYSIWYG editor with styles more specific to the site, adding layout templates to support quick deployment of content and some custom portals for integrating our other information management systems. A week later with the book and I have the first two knocked over and am on my way with the portals.

I have no experience with Java programming, but luckily there was enough detail to get me started. Because of the lack of knowledge I started right from the beginning and read thoroughly all of the background information on Liferay Portal and the JSR-286 specs. This was quite a laborious experience. Not a lot of the JSR-286 specs made any sense until further on in portal development, but helped as a good reference on the portal boundaries later on.

A very progressive structure is taken in this guide. So much that I found it hard to dive into later chapters out of order. Even just the theme development chapter made more sense once I read the previous chapters. Once I had completed a few chapters I found myself using it a lot as a reference. Especially when developing Struts Portlets.

With the latter chapters on workflow, CMS, WYSIWYG editors, communities and templates and themes I was using code from the book directly in my deployment. The examples applied well to customising Liferay for an intranet CMS environment (luckly for me).

There are little quirks in the code examples where more proof reading would have helped, but these were easily ignored by downloading the example code archive.

This book is not for you if you only want to change the database backend or create a basic theme. Nor if you dislike getting your hands dirty in XML. If on the other hand though you are deploying a Liferay based intranet and want to tie in existing content services or want a unique and flexible public site, then the book is right up your alley.

Overall I am impressed with the depth of the book and will probably be spending a few more weeks working through it as I get time. And I will be sure to post updates about the portals if I start developing any applicable to use outside the company.