20090216 Monday February 16, 2009

A bitty week

Last week was a pretty bitty week, dominated by the need to complete some mandatory, examined web training. I have recently completed similar training in Sun's Unified Storage Products which I found useful. This one is not so focused on technology and while useful in that I learned a couple of things, I really wonder if it was a good use of my time.

Prior to getting stuck in, I made some progress on my web estate including Laconica, planet and glassfish. I got a copy of mingle running on one of my Linux images but made no progress on installing Glassfish. I have taken advice and been recommended to use the Sun installer, but I am being stubborn and want to see if I can use the Ubuntu package installer.

Mind you I got fed up with bash & sh and installed the Korn Shell. I was able to use the package manager which is cool. I was expecting that some Linux religous view, or over zealous conformance with the various licenes would prohibit its inclusion, but it works fine. Since I shall only be using it for scripts, I don't need to write a global .kshrc and install it where ever it would need to be. What broke the Camel's back? I felt I needed $(). I had been lectured by Chris Gerhard about using this syntax a while ago because it supports nesting and finally came across a case where it was needed, or at least, coding speed and my skills meant that I decided to move over to it. (It does mean that anything I write may be harder for other Linux users to adopt.) So I'll write in ksh, and port to sh.

I ended the week on Sunday at the Chichester Smith and Western, where the atmosphere, decor and music are fun and the portions enormous.

tags:

              

(2009-02-16 10:41:12.0) Permalink Comments [1]

Trusting the customer in the hospitality trade

Or where to get cheap food and drink. The Guardian last week seemed quite keen to publicise some bars and restaurants that offer you the opportunity to pay what you think they're worth, in London and Berlin.

tags:

              

(2009-02-16 02:44:06.0) Permalink

Influencing Planet's output name space

Earlier, last week on the planet developers mail list, Fredric Muller writes

From the help file I read:
# The following provide defaults for each template:
# output_dir: Directory to place output files

Now I am trying to figure out how to have one of those template file
output in a different directory (like they all go into /var/www/planet/
and I would like one of them to go to /var/www/ ).

I can think of a couple of ways of solving this problem. My first way, which may not be the simplest, is based on the fact that I have several planet instances and for the most advanced and thought out installation I have answered this problem as follows. It is designed to answer another problem and so might be overkill.

  • I install planet into its own user and hence home directory.
  • I plan to run more than one planet so,
  • I create a sub directory for each instance
  • I create a Logs directory since I plan to run the planets from cron, pipe the logs into files and keep them for a while. Both the logs and the log name control files are kept here.
  • In the instance sub directories I place the config.ini file and the template sources; the index.tmpl will also be different as will any images used to decorate the planet html file such as feed logos or page decoration
  • In the home directory I create a shell script, which calls planet.py to act as the argument to cron and a crontab source file.
  • test the script for each instance of Planet
  • set the crontab using the source file

because I have multiple config.ini's and index.tmpl files, I can (and do) have multiple output directories and also ensure that the HTML pages meet my look and feel requirements. I do this at http://davelevy.dyndns.info/planet/davelevy and http://davelevy.dyndns.info/planet/g3 and on my development site have a standard planet venus and a mingle solution. I shall be moving the two planets above shortly so I suggest that you don't rely on them for a while. Within Sun's firewall, I have a community feed and one for me (like planet davelevy above) that uses this technique. The original requirement was based on the need for quite different config.ini files, with different input feed lists but Fredric's case is also solved using the technique.

I also have a script to tidy up the logs, maybe I should publish them all. (If you want'em comment or reply to the planet development list and ask. )

The second answer for Fredric's case, is that since I encapsulate ${HOME}/planet.py into a script, I could always end the script with an appropriate cp command, provided there was no contention for the name /var/www/index.html.

tags:

              

(2009-02-16 02:39:10.0) Permalink

Innovate on OpenSolaris
   in London

  Subscribe to this blog XML

  Now referenced at is.gd,
    http://is.gd/1BW3h

  AddThis Feed Button

  

  See my delicious tag cloud, or
  follow it using a feed reader.

  Also my sun mediacaster page

  Link to my FOAF file

News
Recent & Interesting
All about my site
Recently at del.icio.us
links
Article Index
archives

  2009

  2008

  2007

  2006

  2005

  2004

Blogosphere

Locations of visitors to this page >
referers