From: Tom Anderson on
On Mon, 5 Oct 2009, John B. Matthews wrote:

> In article <4ac9cdeb$0$8424$ec3e2dad(a)unlimited.usenetmonster.com>,
> "Kenneth P. Turvey" <evoturvey(a)gmail.com> wrote:
>
>> On Mon, 05 Oct 2009 03:31:51 -0700, ck wrote:
>>
>>> On Oct 5, 1:08 pm, "Kenneth P. Turvey" <evotur...(a)gmail.com> wrote:
>>>> On Mon, 05 Oct 2009 07:12:05 +0000, Kenneth P. Turvey wrote:
>>>>
>>>>>>> http://www.electricsenator.net/2009/10/03/1254618530821.html
>>>
>>> Is the page garbled, or there is no CSS at all, page(s) is/are
>>> confusing?
>>
>> It should look fine. It is running on my test server and I've been
>> having some problems with it. It will probably be down for few minutes
>> off and on for the next few days, but you shouldn't have a problem with
>> it 99% of the time.
>
> The article is informative and quite readable; it just looks as it might
> if styles had been disabled in the browser.

It looks fine to me.

The article made me laugh, because although it purports to be about
setting up Hudson, it's almost all about setting up other bits of software
which are prerequisites for Hudson. That is of course entirely reasonable,
since those things do have to be set up - but it drives home how
straightforward Hudson is to set up!

tom

--
Imagine that, the Battle of Seattle, the February Revolution, the Storming
of the Bastille, the Brixton uprising, the break-in party at Hackney
Town Hall and Wat Tyler's army ransacking the Tower, all at the same time.
From: John B. Matthews on
In article <alpine.DEB.1.10.0910052107380.10051(a)urchin.earth.li>,
Tom Anderson <twic(a)urchin.earth.li> wrote:

>>> http://www.electricsenator.net/2009/10/03/1254618530821.html

> It looks fine to me.

Ah, I see screen.css loads now. It probably looks like it was meant to,
sans-serif body text and all.

body {
font-family: Trebuchet MS, Lucida Grande, ..., sans-serif;
....
}

Looks good; reads bad; old war:

<http://en.wikipedia.org/wiki/Wikipedia_talk:Serif_or_sans-serif>

What were we talking about? Oh, yeah, thorough article.

--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>
From: Kenneth P. Turvey on
On Mon, 05 Oct 2009 21:11:13 +0100, Tom Anderson wrote:

[Snip]
> The article made me laugh, because although it purports to be about
> setting up Hudson, it's almost all about setting up other bits of
> software which are prerequisites for Hudson. That is of course entirely
> reasonable, since those things do have to be set up - but it drives home
> how straightforward Hudson is to set up!

That's actually true. The Hudson portion itself is not really that hard
to set up, but there is a lot of infrastructure there that needs to be
going first. Also, for public sites, I may have made is seem more simple
than it really needs to be. I disabled the sandboxing of Hudson in
Tomcat. Although this makes it much easier to set up, and is perfectly
fine for an intranet installation, it really isn't a good idea for a
publicly available web server. Hudson allows users to run arbitrary
commands on the server, and without sandboxing it could be a farily
dangerous application to have on your server. The problem is that
deciding what permissions to give it is not straightforward. It really
depends on what kinds of jobs Hudson is going to be running. If you are
only going to use it to run Grails apps and checkout from git, that's not
too complicated, but as you add more complexity to the builds, you also
have to add more complexity to the security policy. I haven't thought
through all the implications yet. When I do, maybe I'll post something
on it.

I hope it was useful for you.


--
Kenneth P. Turvey <evoturvey(a)gmail.com>

http://www.electricsenator.net