Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.misc > #651 > unrolled thread

Why I went from Wordpress to Pelican

Back to article view | Back to comp.misc

Contents

  Why I went from Wordpress to Pelican RS Wood  <rswood@therandymon.com> - 2014-02-21 11:42 +0000
    Re: Why I went from Wordpress to Pelican "tdk" <forum.tdk@squte.com> - 2014-02-21 06:28 +0628
      Re: Why I went from Wordpress to Pelican RS Wood <rsw@therandymon.com> - 2014-02-21 13:16 +0000
        Re: Why I went from Wordpress to Pelican "tdk" <forum.tdk@squte.com> - 2014-02-21 08:50 +0850
        Re: Why I went from Wordpress to Pelican Lance Orner <lance@orner.invalid.net> - 2014-02-24 18:50 -0800
          Re: Why I went from Wordpress to Pelican "tdk" <forum.tdk@squte.com> - 2014-02-25 02:58 -0600
            Re: Why I went from Wordpress to Pelican Johannes Grassler <jgr-usenet@btw23.de> - 2014-02-25 10:07 +0000
      Re: Why I went from Wordpress to Pelican Alvaro Martínez <alvaro@elcodiguero.com> - 2014-02-22 21:30 -0200

#651 — Why I went from Wordpress to Pelican

From the Because it flies like a Penguin department:
Title: Using pelican for serving this blog
Author: mrunge
Date: Wed, 19 Feb 2014 09:40:00 -0500
Link: http://www.matthias-runge.de/deprecating-wordpress.html

[image 1]

For my own blog, I recently deprecated wordpress, in favor of using pelican.
The package was recently added to Fedora. It's quite simple and does not
require php, mysql, and a memcached running on a webserver.

In the past, the number of attempts to get into this host increased
significantly. During Linux-Tag-Oldenburg last year, we had a wordpress
installation to serve the schedule. It just failed when more persons tried to
edit the same document.

Pelican uses structured text files, which are being processed once to html
files. This means, one can use awesome tools like vim and git.

Links:
[1]: http://planet.fedoraproject.org/images/heads/default.png (image)

[toc] | [next] | [standalone]

#653

Another link is: 
http://blog.getpelican.com/
From which "Pelican is a static site generator".
In other words it's nothing like wordpress which allows comments, users, stats, 
etc. It's basically a mark up language processor.


-- 
View this thread at http://squte.com/node/4701#comment-10730

[toc] | [prev] | [next] | [standalone]

#654

On Fri, 21 Feb 2014 06:28:08 +0628
"tdk" <forum.tdk@squte.com> wrote:

> Another link is: 
> http://blog.getpelican.com/
> From which "Pelican is a static site generator".
> In other words it's nothing like wordpress which allows comments, users, stats, 
> etc. It's basically a mark up language processor.
> 
> 
> -- 
> View this thread at http://squte.com/node/4701#comment-10730
> 

Any idea what happened to Bash Blogger?  It was a set of scripts that
allowed you to maintain a set of static web pages from the Bash command
prompt.  I was impressed by it a year or two ago, but lost track and
it's not clear the project even exists anymore.

(congrats on squte by the way - it's awesome).

[toc] | [prev] | [next] | [standalone]

#662

> Any idea what happened to Bash Blogger?
It looks like it was last updated in 2007: http://bashblogger.sourceforge.net/
I'm not sure what the advantage is in using bash over python ruby etc.
> (congrats on squte by the way - it's awesome).
Thank you very much. 
If the site is a success then the moderation will be even better, and more people 
will be aware of this group. 
So I am grateful for anything anyone does to promote it.
-- 
View this thread at http://squte.com/node/4701#comment-10735

[toc] | [prev] | [next] | [standalone]

#880

On 2014-02-21, RS Wood <rsw@therandymon.com> wrote:
> On Fri, 21 Feb 2014 06:28:08 +0628
> "tdk" <forum.tdk@squte.com> wrote:
>> From which "Pelican is a static site generator".
>> In other words it's nothing like wordpress which allows comments,
>> users, stats, etc. It's basically a mark up language processor.

Yes, but.  I moved to Jekyll from Wordpress, and removing the
dependency on a database to store everything means you can use version
control and Git.

My flow:
* Files are markdown files in a folder
* Create new or modify a modify a markdown file to add a blog post
* Run the jekyll run to compile and launch a local server 
  * I use a Makefile
* When happy with the results, rync compiled folder to main server
* RSS feeds and common headers are all handled

Pelican is similar, but uses Python instead of Ruby.  I'm not a Mac
person, but I just started using Jekyll first, and I use it as a
utility, so the language doesn't much matter.

Stats are handled by Google or whatever.  Comments could use Discus or
similar.

-- 
  Lance Orner (lance@orner.net)

[toc] | [prev] | [next] | [standalone]

#882

> removing the dependency on a database to store everything means you can use version 
> control and Git
That's quite an appealing idea, but ideally the viewers should be able to see the 
page revisions as well. I wonder if there's anything like a Wiki but backed by 
Git?

>  Comments could use Discus or similar
I was thinking of offering a Disqus like system myself, but it would be mirrored 
to and from Usenet. i.e each blog/forum would be a newsgroup, and each post or forum 
topic a thread.


-- 
regards
~tdk
View this thread at http://squte.com/node/4701#comment-10937

[toc] | [prev] | [next] | [standalone]

#895

tdk <forum.tdk@squte.com> wrote:
>> removing the dependency on a database to store everything means you
>> can use version control and Git
> That's quite an appealing idea, but ideally the viewers should be able
> to see the page revisions as well. I wonder if there's anything like a
> Wiki but backed by Git?

There is exactly such a thing: http://ikiwiki.info/

I played around with it a bit recently but found it wanting. It's got
tons of dependencies (those let me discover the hard way that FreeBSD's
ports will happily ignore installed modules when they update Perl), and
despite the author's claim to the contrary, UTF8 input ends up mangled.

That being said, it's a very modular, pleasantly unixy kind of wiki with
lots of attachment points to use for bolting on custom stuff. Given time
I'd fiddle with it a little more, try to fix the UTF8 issues, but since
I'm in a bit of a hurry I'll go with something else for now.

There is another git-backed wiki, Gitit, but that one's written in
Haskell and seems to require Happstack at first glance (ikiwiki is plain
old CGI).

>>  Comments could use Discus or similar
> I was thinking of offering a Disqus like system myself, but it would
> be mirrored to and from Usenet. i.e each blog/forum would be a
> newsgroup, and each post or forum topic a thread.

Now there's sensible thinking on comment functions. More power to you!

Cheers,

Johannes

-- 
GPG Key fingerprint: 446C 3310 168B 97ED 10FB  04C9 7864 8E77 CBAC C90B
Phone: +49 176 24 24 20 83                    http://btw23.de/johannes/

[toc] | [prev] | [next] | [standalone]

#744

tdk wrote:

> Another link is:
> http://blog.getpelican.com/
> From which "Pelican is a static site generator".
> In other words it's nothing like wordpress which allows 
comments, users,
> stats, etc. It's basically a mark up language processor.
> 

I use Pelican myself, and added a Disqus snippet for comments, 
you can also add facebook comments or another similar system.
If you want stats, you can install other systems like awstats, 
piwik, analytics or even cloudflare stats. Users may not be 
that easy, however.

I mean, of course Pelican is no match for Wordpress, and it 
depends on what exactly you want from your posting software. 
But it may be an interesting alternative if you know how to 
handle it and don't need everything WP does.

Few caveats: it is quite crappy if you want to use moderately 
complex text formatting (like using a table with color coded 
information), and if you want control over the resulting HTML, 
you may want to write a "fixer" script to work on the 
generated files. This is not really a problem with Pelican, it 
is more a problem with the reST->HTML conversion.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.misc

csiph-web