Re: let's talk about pyblosxom's future

Sebastian Spaeth <[email protected]> Sat, 09 Jun 2012 17:26:04 +0200
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
--===============7642919208324185957==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=
Content-Transfer-Encoding: quoted-printable

will kahn-greene <[email protected]> writes:

> 1. if we have a list of them, then we can give that list to Pyblosxom=20
> users and it makes it easier to transfer to something else if they want=20
> to (they can just continue to use Pyblosxom ad infinitum if it works for=
=20
> them)

That's what I thought. Perhaps people can share their alternative setups
to help people decide where to migrate to in the (very) long term.

> volt looks really interesting. I think all the urls look the same except=
=20
> for permalink urls. So the only problem I'd have when switching is that=20
> I'd need to redirect existing blog entry permalinks to where they'd live=
=20
> under volt.
>
> Sebastian: Did you solve that problem?

THe location of permalinks is configurable (like anything)

        # Plain page permalink, relative to page URL
        PERMALINK =3D '{time:%Y}/{slug}',

So a blog entry of mine would have e.g.
http://sspaeth.de/2012/on-toilets

But you could add ".html" or tags, or month/day or whatnot. The slug is
automatically calculated, if you need something different, you can
always add a
   slug: MooFoo
in the header of a post. I lost my "conversion script" from pyblosxom
posts to volt posts. The only limitation I've seen so far is that the
posts are all expected to live in a flat directory. You could even add a
"url: oldurl.html" line to your post header and use that as Permalink url.=
=20

Here is the full "voltconf.py" that I am using for my blog:
http://pastebin.com/96hwfuU4

The guy was really responsive to my needs and accepted patches. Also he
has tests for everything :).

Anyway, enough advertisement. :-) As I said, I am not the author, just
contributed a few patches.

Sebastian

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk/TawwACgkQVYX1jMgnoGJedACeOX4SLjFYK9+57eEKzYnoVzmn
Ub4An2ARROsytv9baWd4qTdR/DGHUscY
=qp8H
-----END PGP SIGNATURE-----
--=-=-=--


--===============7642919208324185957==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--===============7642919208324185957==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

--===============7642919208324185957==--