A few comments on tg-admin toolbox

[bon...@gmail.com]

Hi,

I just tested this new thing for the first time and have the following
comments :

1. Why launch a browser on the machine running it ? I run it on a
headless server(though VNCed) and would only want to access it from my
notebook.

2. The Turbogear logo at the bottom overlap with the catwalk item. This
I believe is related to the CSS and what browser is in use. Mine is FF
1.5. On the server where Conqueror is launched unexpectedly(see above),
the layout is fine and the logo is tugging bottom.

[Lee McFadden]

There is an option to launch the toolbox without launching a browser:

tg-admin toolbox -n

However, at the moment (or at least on the checkout I'm running) there
doesn't seem to be a way to make the hosts allowed to use the toolbox
anything other than 127.0.0.1. I'll take a look into this and see if
I can get a patch sorted.

In the meantime, if you're happy to edit the turbogears code, you can
do the following:

* open <checkout-dir>/turbogears/command/__init__.py
* find line 194
* change the line to: root.catwalk = CatWalk(model, ['127.0.0.1',
'192.168.0.1'])

Obviously, change the second IP address in that list to that of your
laptop and add in any other IP's you want to access the toolbox from.
:)

Lee

[Lee McFadden]

Since Trac seems to be up and down like a yo-yo at the moment, I'm
posting my patch here until I can add it to a ticket like a good
contributor :)

This patch needs some testing, but it's a simple fix so there
shouldn't be any problems with it.

It adds the ability to add "allowed clients (hosts)" to catwalk when
running tg-admin toolbox.

Example:

tg-admin toolbox -n -c 192.168.0.1 -c 192.168.0.2

This will add both 192.168.0.1 and 192.168.0.2 to catwalk's access list.

This patch is for the file /root/trunk/turbogears/command/__init__.py (Rev. 250)

Lee

[Kevin Dangoor]

Patch committed. Thanks!

Kevin

--
Kevin Dangoor
Author of the Zesty News RSS newsreader

email: k...@blazingthings.com
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com