You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(53) |
Feb
(81) |
Mar
(47) |
Apr
(29) |
May
(32) |
Jun
(24) |
Jul
(41) |
Aug
(86) |
Sep
(40) |
Oct
(28) |
Nov
(11) |
Dec
(23) |
| 2004 |
Jan
(32) |
Feb
(54) |
Mar
(30) |
Apr
(28) |
May
(113) |
Jun
(17) |
Jul
(5) |
Aug
(111) |
Sep
(103) |
Oct
(18) |
Nov
(5) |
Dec
(38) |
| 2005 |
Jan
(31) |
Feb
(26) |
Mar
(69) |
Apr
(36) |
May
(45) |
Jun
(35) |
Jul
(11) |
Aug
(25) |
Sep
(9) |
Oct
(27) |
Nov
(4) |
Dec
(11) |
| 2006 |
Jan
(33) |
Feb
(11) |
Mar
(7) |
Apr
(10) |
May
(11) |
Jun
(2) |
Jul
(9) |
Aug
(7) |
Sep
(22) |
Oct
(40) |
Nov
(34) |
Dec
(5) |
| 2007 |
Jan
(21) |
Feb
(23) |
Mar
(28) |
Apr
(1) |
May
(15) |
Jun
(45) |
Jul
(71) |
Aug
(45) |
Sep
(52) |
Oct
(31) |
Nov
(20) |
Dec
(6) |
| 2008 |
Jan
(17) |
Feb
(25) |
Mar
(7) |
Apr
(5) |
May
(9) |
Jun
(3) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(15) |
Aug
(9) |
Sep
(10) |
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
(42) |
Feb
(28) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(7) |
Sep
(19) |
Oct
(14) |
Nov
(27) |
Dec
(14) |
| 2011 |
Jan
(8) |
Feb
(9) |
Mar
(9) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(18) |
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2012 |
Jan
(5) |
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
(13) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(4) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(9) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Chris G <cl...@is...> - 2010-01-29 16:59:49
|
On Fri, Jan 29, 2010 at 11:17:30AM -0500, will kahn-greene wrote: > On 01/29/2010 11:09 AM, Chris G wrote: > > On Fri, Jan 29, 2010 at 10:46:12AM -0500, will kahn-greene wrote: > >> > > Er, you wrote it! :-) > > > > I think what I'm asking is how (if it's possible) one can have pages > > in a blog which aren't posts. My blog is at the following URL:- > > > > http://home.isbd.net/cgi-bin/pyboat.cgi/ > > > > These 'static' pages in the Blue and Blue menu would be at:- > > > > http://home.isbd.net/cgi-bin/pyboat.cgi/static/<name> > > > > I'm just asking how to get pyblosxom to show these pages. > > Wow--well, I feel like a real ninny right now. :p > > That "static" is referring to the pystaticfile plugin which you can get > here: > > http://bluesock.org/~willg/cgi-bin/devtrac.cgi/wiki/pystaticfile > > There are errors on that page, but the url to the plugin still works. I > should fold that plugin into PyBlosxom. > Ah, thank you, just what I needed. > > >> As a side note, after I get PyBlosxom 1.5 out, we should go through and > >> rework all the flavour packs. PyBlosxom 1.5 should make it easier to > >> install them. > >> > > I'll do what I can to help there. I certainly find the existing setup > > rather confusing for various reasons. > > When you say "existing setup" are you referring to the existing flavour > packs or are you referring to how flavours and templates work? > I'm "referring to how flavours and templates work". I'll send a new E-Mail to the list about this. -- Chris Green |
|
From: will kahn-g. <wi...@bl...> - 2010-01-29 16:25:30
|
On 01/29/2010 11:09 AM, Chris G wrote: > On Fri, Jan 29, 2010 at 10:46:12AM -0500, will kahn-greene wrote: >> > Er, you wrote it! :-) > > I think what I'm asking is how (if it's possible) one can have pages > in a blog which aren't posts. My blog is at the following URL:- > > http://home.isbd.net/cgi-bin/pyboat.cgi/ > > These 'static' pages in the Blue and Blue menu would be at:- > > http://home.isbd.net/cgi-bin/pyboat.cgi/static/<name> > > I'm just asking how to get pyblosxom to show these pages. Wow--well, I feel like a real ninny right now. :p That "static" is referring to the pystaticfile plugin which you can get here: http://bluesock.org/~willg/cgi-bin/devtrac.cgi/wiki/pystaticfile There are errors on that page, but the url to the plugin still works. I should fold that plugin into PyBlosxom. >> As a side note, after I get PyBlosxom 1.5 out, we should go through and >> rework all the flavour packs. PyBlosxom 1.5 should make it easier to >> install them. >> > I'll do what I can to help there. I certainly find the existing setup > rather confusing for various reasons. When you say "existing setup" are you referring to the existing flavour packs or are you referring to how flavours and templates work? /will |
|
From: Chris G <cl...@is...> - 2010-01-29 16:10:01
|
On Fri, Jan 29, 2010 at 10:46:12AM -0500, will kahn-greene wrote:
>
> On 01/29/2010 10:31 AM, Chris G wrote:
> > I'm playing with the Blue and Blue flavour at the moment, it has a
> > sidebar on the RHS with several items which have HREFs like:-
> >
> > <a class="menulink" href="$base_url/static/guestbook.html">guestbook</a>
> >
> > Is there something special about that "$base_url/static" bit? As
> > $base_url is generated by pyblosxom I think there must be as there's
> > no way otherwise for the browser to find 'static'.
> >
> > I don't want a 'static' site, I have a server with apache running so I
> > might as well use it.
> >
> > Where should I put files under my $blogdir so that they would appear
> > in 'static' and what other configuration do I need?
>
> "static" is sort of an overloaded term.
>
Yes, I realise that, the Blue and Blue menu just happens to use it I
suspect. It might as well be 'cabbage'.
> Having said that, you'd have to talk to whoever wrote the flavour to
> know what the "static" part indicates and how to install that flavour
> pack. Is there a README or other documentation?
>
Er, you wrote it! :-)
I think what I'm asking is how (if it's possible) one can have pages
in a blog which aren't posts. My blog is at the following URL:-
http://home.isbd.net/cgi-bin/pyboat.cgi/
These 'static' pages in the Blue and Blue menu would be at:-
http://home.isbd.net/cgi-bin/pyboat.cgi/static/<name>
I'm just asking how to get pyblosxom to show these pages.
> As a side note, after I get PyBlosxom 1.5 out, we should go through and
> rework all the flavour packs. PyBlosxom 1.5 should make it easier to
> install them.
>
I'll do what I can to help there. I certainly find the existing setup
rather confusing for various reasons.
--
Chris Green
|
|
From: will kahn-g. <wi...@bl...> - 2010-01-29 15:46:21
|
"static" is sort of an overloaded term. Having said that, you'd have to talk to whoever wrote the flavour to know what the "static" part indicates and how to install that flavour pack. Is there a README or other documentation? As a side note, after I get PyBlosxom 1.5 out, we should go through and rework all the flavour packs. PyBlosxom 1.5 should make it easier to install them. /will On 01/29/2010 10:31 AM, Chris G wrote: > I'm playing with the Blue and Blue flavour at the moment, it has a > sidebar on the RHS with several items which have HREFs like:- > > <a class="menulink" href="$base_url/static/guestbook.html">guestbook</a> > > Is there something special about that "$base_url/static" bit? As > $base_url is generated by pyblosxom I think there must be as there's > no way otherwise for the browser to find 'static'. > > I don't want a 'static' site, I have a server with apache running so I > might as well use it. > > Where should I put files under my $blogdir so that they would appear > in 'static' and what other configuration do I need? |
|
From: Chris G <cl...@is...> - 2010-01-29 15:32:13
|
I'm playing with the Blue and Blue flavour at the moment, it has a
sidebar on the RHS with several items which have HREFs like:-
<a class="menulink" href="$base_url/static/guestbook.html">guestbook</a>
Is there something special about that "$base_url/static" bit? As
$base_url is generated by pyblosxom I think there must be as there's
no way otherwise for the browser to find 'static'.
I don't want a 'static' site, I have a server with apache running so I
might as well use it.
Where should I put files under my $blogdir so that they would appear
in 'static' and what other configuration do I need?
--
Chris Green
|
|
From: Chris G <cl...@is...> - 2010-01-29 13:07:15
|
On Fri, Jan 29, 2010 at 11:36:37AM +0000, Chris G wrote:
>
> I'll try one of the others and report on that as well.
>
Ah, typical, I just tried pyblosxom-grey and it works perfectly after
fixing the .css file references. I also realised that you don't need
to remove the .html from the file names.
I tried mainlyGreen again (without removing the .html) and it fails
exactly as I reported still.
I've tried some others as well, results as follows:-
1024px - fails, same error as with mainlyGreen
Blue and Blue - works OK
Grey - works OK
I've not tried RDF or Snarfed.
--
Chris Green
|
|
From: Chris G <cl...@is...> - 2010-01-29 11:36:47
|
On Thu, Jan 28, 2010 at 06:03:13PM -0500, will kahn-greene wrote:
> What doesn't work about them? Can you be more specific?
>
Well I tried mainlyGreen. First let me check that what I did to
install it was correct:-
In the flavours directory of my newly installed (and working)
blog I renamed the default html.flav dierctory to html.flav.original
I unpacked mainlygreen002.tar.gz to produce a new html.flav
directory in the flavours directory.
I renamed the files inside the new html.flav directory to remove
the .html suffix, I assume the suffix is there so that the files
could be used directly in the entries tree.
When I run my blog I get the following error in Firefox:-
A server error occurred. Please contact the administrator.
The apache error log has:-
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] Traceback (most recent call last):
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] File "/usr/lib/python2.6/wsgiref/handlers.py", line 93, in run
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] self.result = application(self.environ, self.start_response)
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/pyblosxom.py", line 452, in __call__
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] return [self.run_pyblosxom(env, start_response)]
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/pyblosxom.py", line 444, in run_pyblosxom
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] p.run()
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/pyblosxom.py", line 169, in run
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] blosxom_handler(self._request)
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/pyblosxom.py", line 928, in blosxom_handler
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] renderer.render()
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/renderers/blosxom.py", line 307, in render
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] data['content-type'] = self.flavour['content_type'].strip()
[Fri Jan 29 11:29:12 2010] [error] [client 192.168.1.4] KeyError: 'content_type'
I'll try one of the others and report on that as well.
>
> On 01/28/2010 05:28 PM, Chris G wrote:
> > I seem to remember I found these rather confusing before! :-)
> >
> > I can't make any of the flavours at http://pyblosxom.sourceforge.net/registry/flavours/
> > work with pyblosxom 1.5, I suspect they're all rather old.
> >
> > Are there any newer ones around, like the one used on the pyblosxom
> > site itself for example?
>
--
Chris Green
|
|
From: Chris G <cl...@is...> - 2010-01-29 11:20:53
|
On Thu, Jan 28, 2010 at 08:15:25PM -0500, will kahn-greene wrote:
> On 01/28/2010 03:51 PM, Chris G wrote:
> >
> > After a clean installation if I run 'pyblosxom-cmd create<dir>' in
> > the installed pyblosxom directory (i.e. the directory where there is a
> > data directory and the Pyblosxom directory) then the create works, but
> > if I run it anywhere els it fails with the error I reported.
>
> Ahh... that might be a bug in the setup.py code. I just ditched the
> MANIFEST.in file and maybe that's still needed. I'll take a look at it
> tomorrow.
>
Thanks Will.
By the way I think part of my problem with installing 1.5 was that it
is actually much simpler than it used to be. I.e. just about *all*
one needs to do is:-
Unpack the code
run 'python setup.py install'
run 'pyblosxom-cmd create ./blog/'
Then go and configure a few things. I had been reading what is in the docs
directory and doing stuff I found in there before running pyblosxom-cmd
and I think that's where I was getting a bit lost. I also hadn't
realised (thought through properly that is!) that no part of the
unpacked tar file is needed for the installation to work after you've
done what's above. I was somehow thinking that stuff in either the
pyblosxom or the Pyblosxom directories had to be visible to apache for
it to work.
(I had also added to my confusion by installing on my headless server
system via an NFS mount - that's my problem!)
--
Chris Green
|
|
From: will kahn-g. <wi...@bl...> - 2010-01-29 01:15:34
|
On 01/28/2010 03:51 PM, Chris G wrote: > On Thu, Jan 28, 2010 at 08:30:29PM +0000, Chris G wrote: >> On Thu, Jan 28, 2010 at 02:16:14PM -0500, will kahn-greene wrote: >>> On 01/28/2010 02:03 PM, Chris G wrote: >>>> I used pyblosxom for a while around version 1.3 (I think) and I'm now >>>> back trying it again. I'm not doing too well at the moment. I'm >>>> trying to install the 1.5 beta version on ubuntu 9.10 server. >>>> >>>> So, I'll run through what I have done:- >>>> >>>> Get the code >>>> >>>> svn co https://pyblosxom.svn.sourceforge.net/svnroot/pyblosxom/trunk/pyblosxom/ pyblosxom >>>> >>>> As root, run the install >>>> >>>> python setup.py install >>> >>> That should have installed Python as a site-package and the >>> pyblosxom-cmd command in bin. >>> >> Yes, it has, well nearly:- >> >> chris@server:~$ which pyblosxom-cmd >> /usr/local/bin/pyblosxom-cmd >> chris@server:~$ >> >>> After doing that, to create a blog you do: >>> >>> % pyblosxom-cmd create<dir> >>> >>> and that's it. PyBlosxom builds the directory structure for your blog >>> with flavour files and pyblosxom.cgi and config.py files. >>> >> Yes, that's where I'm getting the error I was reporting:- >> >> chris@server:~$ pyblosxom-cmd create xxx > > ... and I think I have maybe found the problem or at least some of it. > > After a clean installation if I run 'pyblosxom-cmd create<dir>' in > the installed pyblosxom directory (i.e. the directory where there is a > data directory and the Pyblosxom directory) then the create works, but > if I run it anywhere els it fails with the error I reported. Ahh... that might be a bug in the setup.py code. I just ditched the MANIFEST.in file and maybe that's still needed. I'll take a look at it tomorrow. /will |
|
From: will kahn-g. <wi...@bl...> - 2010-01-28 23:03:26
|
What doesn't work about them? Can you be more specific? On 01/28/2010 05:28 PM, Chris G wrote: > I seem to remember I found these rather confusing before! :-) > > I can't make any of the flavours at http://pyblosxom.sourceforge.net/registry/flavours/ > work with pyblosxom 1.5, I suspect they're all rather old. > > Are there any newer ones around, like the one used on the pyblosxom > site itself for example? |
|
From: Chris G <cl...@is...> - 2010-01-28 22:29:13
|
I seem to remember I found these rather confusing before! :-) I can't make any of the flavours at http://pyblosxom.sourceforge.net/registry/flavours/ work with pyblosxom 1.5, I suspect they're all rather old. Are there any newer ones around, like the one used on the pyblosxom site itself for example? -- Chris Green |
|
From: Chris G <cl...@is...> - 2010-01-28 20:52:37
|
On Thu, Jan 28, 2010 at 08:30:29PM +0000, Chris G wrote: > On Thu, Jan 28, 2010 at 02:16:14PM -0500, will kahn-greene wrote: > > On 01/28/2010 02:03 PM, Chris G wrote: > > > I used pyblosxom for a while around version 1.3 (I think) and I'm now > > > back trying it again. I'm not doing too well at the moment. I'm > > > trying to install the 1.5 beta version on ubuntu 9.10 server. > > > > > > So, I'll run through what I have done:- > > > > > > Get the code > > > > > > svn co https://pyblosxom.svn.sourceforge.net/svnroot/pyblosxom/trunk/pyblosxom/ pyblosxom > > > > > > As root, run the install > > > > > > python setup.py install > > > > That should have installed Python as a site-package and the > > pyblosxom-cmd command in bin. > > > Yes, it has, well nearly:- > > chris@server:~$ which pyblosxom-cmd > /usr/local/bin/pyblosxom-cmd > chris@server:~$ > > > After doing that, to create a blog you do: > > > > % pyblosxom-cmd create <dir> > > > > and that's it. PyBlosxom builds the directory structure for your blog > > with flavour files and pyblosxom.cgi and config.py files. > > > Yes, that's where I'm getting the error I was reporting:- > > chris@server:~$ pyblosxom-cmd create xxx ... and I think I have maybe found the problem or at least some of it. After a clean installation if I run 'pyblosxom-cmd create <dir>' in the installed pyblosxom directory (i.e. the directory where there is a data directory and the Pyblosxom directory) then the create works, but if I run it anywhere els it fails with the error I reported. -- Chris Green |
|
From: Chris G <cl...@is...> - 2010-01-28 20:41:37
|
On Thu, Jan 28, 2010 at 02:16:14PM -0500, will kahn-greene wrote: > On 01/28/2010 02:03 PM, Chris G wrote: > > I used pyblosxom for a while around version 1.3 (I think) and I'm now > > back trying it again. I'm not doing too well at the moment. I'm > > trying to install the 1.5 beta version on ubuntu 9.10 server. > > > > So, I'll run through what I have done:- > > > > Get the code > > > > svn co https://pyblosxom.svn.sourceforge.net/svnroot/pyblosxom/trunk/pyblosxom/ pyblosxom > > > > As root, run the install > > > > python setup.py install > > That should have installed Python as a site-package and the > pyblosxom-cmd command in bin. > Yes, it has, well nearly:- chris@server:~$ which pyblosxom-cmd /usr/local/bin/pyblosxom-cmd chris@server:~$ > After doing that, to create a blog you do: > > % pyblosxom-cmd create <dir> > > and that's it. PyBlosxom builds the directory structure for your blog > with flavour files and pyblosxom.cgi and config.py files. > Yes, that's where I'm getting the error I was reporting:- chris@server:~$ pyblosxom-cmd create xxx pyblosxom-cmd version 1.5 dev Creating '/home/chris/xxx'... Creating '/home/chris/xxx/entries'... Creating '/home/chris/xxx/plugins'... Creating file '/home/chris/xxx/config.py'... Traceback (most recent call last): File "/usr/local/bin/pyblosxom-cmd", line 5, in <module> pkg_resources.run_script('pyblosxom==1.5', 'pyblosxom-cmd') File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 448, in run_script self.require(requires)[0].run_script(script_name, ns) File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1166, in run_script execfile(script_filename, namespace, namespace) File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/EGG-INFO/scripts/pyblosxom-cmd", line 25, in <module> sys.exit(command_line_handler("pyblosxom-cmd", sys.argv)) File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/commandline.py", line 431, in command_line_handler return f(command, argv) File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/commandline.py", line 268, in create_blog _copyfile(source, d, "config.py", fix=True) File "/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/commandline.py", line 248, in _copyfile fp = open(os.path.join(frompath, fn), "r") IOError: [Errno 2] No such file or directory: '/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/data/config.py' > Sounds like you should read through the README and INSTALL files. There > are a lot of changes in PyBlosxom 1.5 specifically to make it easy to > install. > I think I have followed the README and INSTALL. Looking harder at the above error it seems as if there should be a config.py in the installation somewhere that can't be found. -- Chris Green |
|
From: will kahn-g. <wi...@bl...> - 2010-01-28 19:16:23
|
On 01/28/2010 02:03 PM, Chris G wrote: > I used pyblosxom for a while around version 1.3 (I think) and I'm now > back trying it again. I'm not doing too well at the moment. I'm > trying to install the 1.5 beta version on ubuntu 9.10 server. > > So, I'll run through what I have done:- > > Get the code > > svn co https://pyblosxom.svn.sourceforge.net/svnroot/pyblosxom/trunk/pyblosxom/ pyblosxom > > As root, run the install > > python setup.py install That should have installed Python as a site-package and the pyblosxom-cmd command in bin. After doing that, to create a blog you do: % pyblosxom-cmd create <dir> and that's it. PyBlosxom builds the directory structure for your blog with flavour files and pyblosxom.cgi and config.py files. Sounds like you should read through the README and INSTALL files. There are a lot of changes in PyBlosxom 1.5 specifically to make it easy to install. /will |
|
From: Chris G <cl...@is...> - 2010-01-28 19:08:27
|
I used pyblosxom for a while around version 1.3 (I think) and I'm now
back trying it again. I'm not doing too well at the moment. I'm
trying to install the 1.5 beta version on ubuntu 9.10 server.
So, I'll run through what I have done:-
Get the code
svn co https://pyblosxom.svn.sourceforge.net/svnroot/pyblosxom/trunk/pyblosxom/ pyblosxom
As root, run the install
python setup.py install
So far, so good, no errors. However this is where I get a little
confused. I have copied pyblosxom.cgi to my CGI directory, now I
need to get config.py onto my python path. As installed, config.py
is /var/www/pyblosxom/Pyblosxom/data/config.py but I don't really
want it there. Which bits of the tree do I need to move to my
blog directory?
I assumed that I need to move the Pyblosxom directory to become
the blog directory on my web server, so
mv /var/www/pyblosxom/Pyblosxom /var/www/boatBlog
and my 'basedir' is thus /var/www/boatBlog. Have I got this right?
So I put sys.path.append("/var/www/boatBlog/data") in pyblosxom.cgi
and when I run the test I get
/usr/lib/cgi-bin/pyblosxom.cgi test
Exception: Plugin directory '%(basedir)s/plugins' does not exist.
Please check your config file
In config.py there is
blogdir = "%(basedir)s"
Is that "%(basedir)s" anything special or just a placeholder, i.e.
should I just replace it with
blogdir = "/var/www/boatBlog"
and create a /var/www/boatBlog/plugins directory? It just seems a
little odd that the plugins directory isn't there already.
Anyway, having done all this I get no errors when I run the test
of the CGI script.
Now, this is where I've run out of steam, when I run
pyblosxom-cmd create ./blog/
I get the following error traceback
root@server:/var/www/pyblosxom# pyblosxom-cmd create ./blog/
pyblosxom-cmd version 1.5 dev
Creating '/var/www/pyblosxom/blog'...
Creating '/var/www/pyblosxom/blog/entries'...
Creating '/var/www/pyblosxom/blog/plugins'...
Creating file '/var/www/pyblosxom/blog/config.py'...
Traceback (most recent call last):
File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
pkg_resources.run_script('pyblosxom==1.5', 'pyblosxom-cmd')
File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 448,
in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1166,
in run_script
execfile(script_filename, namespace, namespace)
File
"/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/EGG-INFO/scripts/pyblosxom-cmd",
line 25, in <module>
sys.exit(command_line_handler("pyblosxom-cmd", sys.argv))
File
"/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/commandline.py",
line 431, in command_line_handler
return f(command, argv)
File
"/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/commandline.py",
line 268, in create_blog
_copyfile(source, d, "config.py", fix=True)
File
"/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/commandline.py",
line 248, in _copyfile
fp = open(os.path.join(frompath, fn), "r")
IOError: [Errno 2] No such file or directory: '/usr/local/lib/python2.6/dist-packages/pyblosxom-1.5-py2.6.egg/Pyblosxom/data/config.py'
Help! :-)
--
Chris Green
|
|
From: chombee <ch...@la...> - 2010-01-20 18:20:17
|
I saw that on hacker news too. His blog looks a lot like a wordpress blog (I guess because he converted a wordpress theme), it doesn't have that 'hacked together by a computer programmer' (as opposed to a graphic or web designer) feel that many pyblosxom blogs have! But if you look there are little things that are a dead giveaway that it's pyblosxom (and I'm not talking about the 'powered by pyblosxom' at the bottom). It sounds like he's using the old version though. He's gonna like 1.5 when it's out! On Wed, Jan 20, 2010 at 11:14:20AM -0600, Erich Heine wrote: > http://happy.cat/blog/Blogging-with-pyBlosxom-2010-01-20.html > > It made the front page of hackernews too!. > > Regards, > Erich > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
|
From: Erich H. <sop...@gm...> - 2010-01-20 17:14:29
|
http://happy.cat/blog/Blogging-with-pyBlosxom-2010-01-20.html It made the front page of hackernews too!. Regards, Erich |
|
From: chombee <ch...@la...> - 2010-01-20 02:19:00
|
I've been thinking about this tumblelog plugin some more. I wanted to
add markdown support to it and did so in the copy that I'm running. I
just assumed that the top-level object of each YAML entry is a
dictionary and that each of the values in the dictionary is a string
that should be treated as markdown text (apart from the value of
'template_name' which is used to choose the entry's template). This
actually works fine for me but the assumptions really restrict the
flexibility of YAML, and it feels like a hack.
I think a better way of doing it might be to use PyYAML's ability to
load instances of user Python classes directly from YAML documents. For
each type of post you would add a class to the tumblelog.py file:
Link(yaml.YAMLObject), Quote(yaml.YAMLObject), etc. The content of an
entry would then look like this:
!Link
url: http://www.whatever.com
name: Whatever
desc: >
blah blah blah blah fkdlf fds f
ffds f fblah fd ff sd fds f fds.
tags: ['whatever','blah']
PyYAML knows to load a Link object from that YAML document. The Link
class can do what it wants with the fields, e.g. treating the `desc`
field as markdown text (or transforming it in any other way, for that
matter), the `tags` field as a list, etc. And the link class knows the
name of its template, you don't have to explicitly give `template_name`
in every new post that you create. Other classes can handle their own
fields in their own ways, and they can do whatever processing is
necessary with them, so much power is gained.
Each of these entry classes then has an entrydata() method that returns
a dict with `template_name` and whatever other fields that type of entry
has. So the entryparser plugin would load the yaml file with PyYAML,
call the entrydata() method of the resulting object to get a dictionary,
and return the dictionary to pyblosxom.
The only disadvantage seems to be that if the user wants to invent a new
type of post they now need to add a new class to tumblelog.py, as well
as adding a new template to each each of their flavours as before.
Well, so far the simpler and more limited version of the plugin works
for me, so I'll probably stick with it.
On Tue, Jan 05, 2010 at 09:01:31PM +0000, chombee wrote:
> This is a very simple plugin to make your PyBlosxom blog 'tumblelog'
> capable. It's an entry parser plugin that lets you write entries in
> YAML, and additionally lets those entries specify which story template
> they should be rendered with, so that you can have many different story
> templates in your flavour and entries of different types can have
> different YAML structures and different templates, so they ultimately
> get rendered differently by PyBlosxom even though they appear together
> on the same page. I keep trying to come up with a good way of explaining
> but not really succeeding, it's very simple really. It's explained
> better on the web page:
>
> http://github.com/seanh/PyBlosxom-tumblelog
>
> This is a very simple tumblelog plugin. In the future I'll probably want
> to add markdown support to it, and maybe have it figure out the template
> to use for a post depending on the post's category rather than having
> each post specify its template.
>
> Thanks to Will for tips on how to implement it.
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
|
|
From: chombee <ch...@la...> - 2010-01-20 02:04:13
|
Ok. It'd be easy to do both: log an error message and also return a dict with 'title' and 'body' containing error messages. Would requesting an error template assume the user's flavour has such a template? Maybe error templates should be added to the default flavours? Is there a way that the plugin could check for the existence of an error template in the requested flavour, and if it doesn't exist fall back on the story template? On Tue, Jan 19, 2010 at 06:23:43PM -0500, will kahn-greene wrote: > I've been thinking about this very issue for a while. I think in this > case, it's unlikely that the data can't be made public (e.g. passwords > should never show up on the site), so I'd have your plugin return a > title/body dict and either request an error template or use the story > template. > > That way if the user checks his/her blog, he/she will see the error and > can fix the problem. > > My guess is that it's more likely the user will check his/her blog after > posting than would check the pyblosxom log. > > It's probably a few lines of code to build an error entry or to log > something to the log... You could make it configurable. > > That's off the top of my head. I'd be interested in hearing other > peoples' thoughts. It'd probably be something useful for the "writing a > plugin" part of the manual. > > /will > > > On 01/19/2010 06:11 PM, chombee wrote: > > Is there a 'right thing' for this entryparser plugin to do if it catches > > an exception because a user's YAML entry didn't parse? I guess you > > should use pyblosxom's logger instance to log an error, but what should > > the parse method return to pyblosxom given that the entry could not be > > parsed? > > > > On Tue, Jan 05, 2010 at 09:01:31PM +0000, chombee wrote: > >> This is a very simple plugin to make your PyBlosxom blog 'tumblelog' > >> capable. It's an entry parser plugin that lets you write entries in > >> YAML, and additionally lets those entries specify which story template > >> they should be rendered with, so that you can have many different story > >> templates in your flavour and entries of different types can have > >> different YAML structures and different templates, so they ultimately > >> get rendered differently by PyBlosxom even though they appear together > >> on the same page. I keep trying to come up with a good way of explaining > >> but not really succeeding, it's very simple really. It's explained > >> better on the web page: > >> > >> http://github.com/seanh/PyBlosxom-tumblelog > >> > >> This is a very simple tumblelog plugin. In the future I'll probably want > >> to add markdown support to it, and maybe have it figure out the template > >> to use for a post depending on the post's category rather than having > >> each post specify its template. > >> > >> Thanks to Will for tips on how to implement it. > >> > >> > >> ------------------------------------------------------------------------------ > >> This SF.Net email is sponsored by the Verizon Developer Community > >> Take advantage of Verizon's best-in-class app development support > >> A streamlined, 14 day to market process makes app distribution fast and easy > >> Join now and get one step closer to millions of Verizon customers > >> http://p.sf.net/sfu/verizon-dev2dev > >> _______________________________________________ > >> pyblosxom-users mailing list > >> pyb...@li... > >> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > > > > > > ------------------------------------------------------------------------------ > > Throughout its 18-year history, RSA Conference consistently attracts the > > world's best and brightest in the field, creating opportunities for Conference > > attendees to learn about information security's most important issues through > > interactions with peers, luminaries and emerging and established companies. > > http://p.sf.net/sfu/rsaconf-dev2dev > > _______________________________________________ > > pyblosxom-users mailing list > > pyb...@li... > > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
|
From: will kahn-g. <wi...@bl...> - 2010-01-19 23:23:52
|
I've been thinking about this very issue for a while. I think in this case, it's unlikely that the data can't be made public (e.g. passwords should never show up on the site), so I'd have your plugin return a title/body dict and either request an error template or use the story template. That way if the user checks his/her blog, he/she will see the error and can fix the problem. My guess is that it's more likely the user will check his/her blog after posting than would check the pyblosxom log. It's probably a few lines of code to build an error entry or to log something to the log... You could make it configurable. That's off the top of my head. I'd be interested in hearing other peoples' thoughts. It'd probably be something useful for the "writing a plugin" part of the manual. /will On 01/19/2010 06:11 PM, chombee wrote: > Is there a 'right thing' for this entryparser plugin to do if it catches > an exception because a user's YAML entry didn't parse? I guess you > should use pyblosxom's logger instance to log an error, but what should > the parse method return to pyblosxom given that the entry could not be > parsed? > > On Tue, Jan 05, 2010 at 09:01:31PM +0000, chombee wrote: >> This is a very simple plugin to make your PyBlosxom blog 'tumblelog' >> capable. It's an entry parser plugin that lets you write entries in >> YAML, and additionally lets those entries specify which story template >> they should be rendered with, so that you can have many different story >> templates in your flavour and entries of different types can have >> different YAML structures and different templates, so they ultimately >> get rendered differently by PyBlosxom even though they appear together >> on the same page. I keep trying to come up with a good way of explaining >> but not really succeeding, it's very simple really. It's explained >> better on the web page: >> >> http://github.com/seanh/PyBlosxom-tumblelog >> >> This is a very simple tumblelog plugin. In the future I'll probably want >> to add markdown support to it, and maybe have it figure out the template >> to use for a post depending on the post's category rather than having >> each post specify its template. >> >> Thanks to Will for tips on how to implement it. >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> pyblosxom-users mailing list >> pyb...@li... >> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > |
|
From: chombee <ch...@la...> - 2010-01-19 23:15:06
|
Is there a 'right thing' for this entryparser plugin to do if it catches an exception because a user's YAML entry didn't parse? I guess you should use pyblosxom's logger instance to log an error, but what should the parse method return to pyblosxom given that the entry could not be parsed? On Tue, Jan 05, 2010 at 09:01:31PM +0000, chombee wrote: > This is a very simple plugin to make your PyBlosxom blog 'tumblelog' > capable. It's an entry parser plugin that lets you write entries in > YAML, and additionally lets those entries specify which story template > they should be rendered with, so that you can have many different story > templates in your flavour and entries of different types can have > different YAML structures and different templates, so they ultimately > get rendered differently by PyBlosxom even though they appear together > on the same page. I keep trying to come up with a good way of explaining > but not really succeeding, it's very simple really. It's explained > better on the web page: > > http://github.com/seanh/PyBlosxom-tumblelog > > This is a very simple tumblelog plugin. In the future I'll probably want > to add markdown support to it, and maybe have it figure out the template > to use for a post depending on the post's category rather than having > each post specify its template. > > Thanks to Will for tips on how to implement it. > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users |
|
From: chombee <ch...@la...> - 2010-01-19 16:03:13
|
On Sat, Jan 16, 2010 at 09:57:32AM -0500, Joseph Reagle wrote: > > [snip]. Any recommendations out there for [web hosts] that make > running a pyblosxom blog easy? (i.e., ssh, shell access, cgi, > .htaccess) http://sdf.org/ You can get a shell account there and either install pyblosxom yourself (which is easily done) or get their motd membership, where they have a system-wide install of pyblosxom available. |
|
From: Joseph R. <re...@mi...> - 2010-01-16 15:21:34
|
I'm thinking I may need to change my web host. Any recommendations out there for those that make running a pyblosxom blog easy? (i.e., ssh, shell access, cgi, .htaccess) |
|
From: chombee <ch...@la...> - 2010-01-05 21:05:00
|
This is a very simple plugin to make your PyBlosxom blog 'tumblelog' capable. It's an entry parser plugin that lets you write entries in YAML, and additionally lets those entries specify which story template they should be rendered with, so that you can have many different story templates in your flavour and entries of different types can have different YAML structures and different templates, so they ultimately get rendered differently by PyBlosxom even though they appear together on the same page. I keep trying to come up with a good way of explaining but not really succeeding, it's very simple really. It's explained better on the web page: http://github.com/seanh/PyBlosxom-tumblelog This is a very simple tumblelog plugin. In the future I'll probably want to add markdown support to it, and maybe have it figure out the template to use for a post depending on the post's category rather than having each post specify its template. Thanks to Will for tips on how to implement it. |
|
From: John P. <jo...@sy...> - 2009-10-14 19:50:21
|
Hello list, I have successfully ported my Blosxom blog to PyBlosxom + Python Paste, and moved from Apache to Nginx and static to dynamic rendering in the process. I have posted some notes on my setup to my blog: http://blog.johnp.net/sites/blog-site-setup I hope that someone finds these useful. I wrote my own version of the Blosxom "archives" plug-in; if anyone's interested I could post the code here. You can see the output on my blog. Please CC any replies to me directly as I'm not subscribed to this list (yet). Cheers, John :^P -- John Pallister jo...@jo... jo...@sy... |