[ckan-dev] Virtualenv tips: how to reload the ini file

Thu Jun 12 05:01:28 UTC 2014

G'Day all,

Thanks to some kindly orientation help from Jason Tan, I have managed to 
get python to reload the development.ini file and proceed onward on the 
path to creating a custom theme....but not without some lingering confusion.

This is a request for advice on how to manage the virtualenv sessions 
properly.

Starting from a fresh PuTTY login, I run $ netstat -lntp and can see 
that there's an existing Python process on a given PID (let's say 4506)

(1) If I open another shell, activate a virtualenv (. 
/usr/lib/ckan/default/bin/activate), and try to run the paster command:

paster serve --reload /etc/ckan/default/development.ini

we will get the message that the server is starting in some other socket 
(eg 5304), and then will get the socket Errno 98 Address already in use.

(2) If I kill the python process manually, and then re-run the paster 
command, the server appears to reload the ini file and start itself 
normally.

It doesn't seem right that I have to manually kill Python before being 
able to run the --reload, but, given that Python should always be 
running, and I don't know how to join (or leave) an existing virtualenv 
session, I'm not sure what else to do.

Thanks for any pointers!

Kind regards,

JB

-- 
John Brisbin
Managing Director, BoaB interactive Pty Ltd
POB 248, MT Molloy QLD 4871

E: john at boab.info
M: 0407 471 565 | P: 07 4094 2172
Skype: boabjohn | Twitter: @boabjohn