Desktop Servers, Take…uh…Three?
How many takes are we up to now?
George Bauer responds to my earlier post:
It’s not ‘Desktop Servers, Take Two’ but ‘Non-Hosted Blogging Software, Take Two’ – as the very same problems arise with every solution that’s not running on a central host.
He’s hits the nail dead-on. However, as with Radio, most of his solutions for Python Desktop Serverall require an always-on machine, always-on Internet connection, and remote access. If you’re someone (like me) who blogs from multiple computers, none of which can effectively be set up as a server (which is what an always-on, always-connected machine is), that doesn’t help.
He does say you can “run PyDS on some central machine with static internet connection and set up remote access (this would make PyDS into a central hosted solution much like MT).” If by “remote access” he means via HTTP (and not something like PC Anywhere, then we’re cooking with gas. That’s something Userland told me you couldn’t do with Radio.
Bottom line: could I install PyDS as a Python app on my web hosting provider account, and log in to it via a URL just like I do with Movable Type (which is installed as a Perl CGI app on my web hosting provider account)?
[Update: Hmm. I just realized if you draft something in MT, when you post it later, it's posted "in the past" at the date you drafted it. I've updated the 'Authored On' field for this post, so I think it will show up closer to the time when I actually posted it, e.g during my lunch today, 04/23/03]
Running PyDS as a central hosted solution?
Greg asks: Bottom line: could I install PyDS as a Python app on my web hosting provider account, and log in to it via a URL just like I do with Movable Type (which is installed as a Perl CGI app on my web hosting provider account)? Short answer: yes …