The git integration shown in the above screenshot is just is the icing on the cake, seriously worth spending some time on this if you spend any length of time at the Terminal.

You will get something like the following:

Then you can start drilling down the folders until you find the exact culprit. In my case a log file had grown to 8 Gig in size.

1. spawn-fcgi: there's a package for it so I just used that :
   PLAIN TEXT
   CODE:

   1. sudo apt-get install spawn-fcgi

2. the stop/start script complained when adding it to the boot/shutdown cycle, but one posted in the comments worked:
   PLAIN TEXT
   CODE:

   1. #!/bin/bash
   2. ### BEGIN INIT INFO
   3. # Provides: php-fastcgi
   4. # Required-Start: $all
   5. # Required-Stop: $all
   6. # Default-Start: 2 3 4 5
   7. # Default-Stop: 0 1 6
   8. # Short-Description: starts the php-fastcgi process
   9. # Description: starts php-fastcgi using start-stop-daemon
   10. ### END INIT INFO
   11. PHP_SCRIPT=/usr/bin/php-fastcgi
   12. FASTCGI_USER=www-data
   13. RETVAL=0
   14. case "$1" in
   15. start)
   16. su - $FASTCGI_USER -c $PHP_SCRIPT
   17. RETVAL=$?
   18. ;;
   19. stop)
   20. killall -9 php5-cgi
   21. RETVAL=$?
   22. ;;
   23. restart)
   24. killall -9 php5-cgi
   25. su - $FASTCGI_USER -c $PHP_SCRIPT
   26. RETVAL=$?
   27. ;;
   28. *)
   29. echo "Usage: php-fastcgi {start|stop|restart}"
   30. exit 1
   31. ;;
   32. esac
   33. exit $RETVAL

3. Next to stop Apache from starting up run:
   PLAIN TEXT
   CODE:

   1. sudo update-rc.d -f apache2 remove

4. On the rewrite front, I needed to add the following to my virtual host configuration to have those seo friendly urls up and running again:
   PLAIN TEXT
   CODE:

   1. try_files $uri $uri/ /index.php;

And locate the lines below to start fine tuning Jetty's memory usage:

As with all types of deletes, recursive or not, use with caution.

For windows use:

1. grails war (your app), in this case epic.war
2. Copy to server
   PLAIN TEXT
   CODE:

   1. scp epic.war user@server:/location

3. On Debian the location for jetty webapps is: /var/lib/jetty/webapps
4. Copy from upload location to the above folder (I used sudo)
5. Change permissions:
   PLAIN TEXT
   CODE:

   1. sudo chown jetty:adm epic-0-0.1.war

6. created a *.xml context file in /etc/jetty/contexts, with something like this [note case is important!!]:
   PLAIN TEXT
   CODE:

   1. <?xml version="1.0"  encoding="ISO-8859-1"?>
   2. <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
   3. <Configure class="org.mortbay.jetty.webapp.WebAppContext">
   4.   <Set name="contextPath">/epic</Set>
   5.   <Set name="war"><SystemProperty name="jetty.home" default="."/>/webapps/epic-0-0.1.war</Set>
   6. </Configure>

7. restart jetty :
   PLAIN TEXT
   CODE:

   1. sudo /etc/init.d/jetty restart

   (try stop/start as well)

8. test with :
   PLAIN TEXT
   CODE:

   1. lynx http://localhost:8080/epic/

9. Nice but I'd like http://localhost/epic/ so enable mod_proxy in apache if you haven't already :
   PLAIN TEXT
   CODE:

   1. a2enmod proxy

10. edit /etc/apache2/mods-enabled/proxy.load and if not present add at end:
    PLAIN TEXT
    CODE:

    1. LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so

11. edit your virtualhost conf file I am using 000-default and add:
    PLAIN TEXT
    CODE:

    1. ProxyRequests Off
    2. <Proxy *>
    3.     Order deny,allow
    4.      Allow from all
    5. </Proxy>
    6. ProxyPass        /epic http://localhost:8080/epic
    7. ProxyPassReverse /epic http://localhost:8080/epic
    8. ProxyPreserveHost On

12. restart apache : 
    PLAIN TEXT
    CODE:

    1. sudo /etc/init.d/apache2 restart

13. now you can
    PLAIN TEXT
    CODE:

    1. lynx http://localhost/epic/

Update: I had omitted the ProxyPreserveHost On from the Apache configuration, which resulted in css, images and external javascripts not loading. It also caused an issue with accessing controllers.

Sources:

• Configuring mod_proxy
• Deploying a web application to Jetty

When you google for the solution I found a number of dead ends, but in the comments for one of them there was a helpful pointer.

When you do an 'ls -la' on sites-enabled (inside /etc/apache2), you will see a symbolic link to the sites-available folder and typically just for the default site (000-default -> default). However in sites-available there's also a default-ssl config file. Creating a symbolic link to this file and reloading apache fixed my problem and now I have apache serving up http over SSL .

1. MySQL : failed to start, complaining about:
   PLAIN TEXT
   CODE:

   1. /etc/init.d/mysql: ERROR: Using expire_logs_days without log_bin crashes
   2. the server. See README.Debian.gz

   Commenting out the expire_logs_days in the my.cnf file allowed me to restart MySQL.

2. After the upgrade of Apache, my virtual hosts weren't working. A quick search via Google pointed me to this post - a quick edit of all of my host files and it was all working again.
3. the php-mysql connector somehow hadn't been upgraded/installed so a quick
   PLAIN TEXT
   CODE:

   1. apt-get install php5-mysql

   fixed that problem.

4. OpenBD : the only thing that remains broken was my tomcat5.5 Open BD install. Tomcat was working fine but Open BD refused to start up complaining about :
   PLAIN TEXT
   CODE:

   1. javax.servlet.ServletException: Open BlueDragon Engine Failed to initialise tags: java.awt.Color

   Since I am not really using it, it's not that important, but at some stage I'd like to get it working again. If you have any suggestions, please leave a comment.

Oops forgot to install XCode (you always forget to install something on a new machine ). Quickly ran the XCode installer, however when I ran the command again I got a new error:

Turns out you need to do a cleanup before attempting to run the command again:

Time to continue the Mapnik install.