From: tychoish <garen@tychoish.com>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: news1142@karl-voit.at, emacs-orgmode@gnu.org
Subject: Re: Minimal overhead Org-mode blogging system
Date: Tue, 17 Jan 2012 13:50:29 -0500 [thread overview]
Message-ID: <20120117185029.GD8376@arendt.tychoish.net> (raw)
In-Reply-To: <CALnw1fT6xujVpqJNS2RxiV62KeEaWg=q-r2Jj+oU5nNiwdSFug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
On Wed, Dec 07, 2011 at 10:50:52PM +0530, Puneeth Chaganti wrote:
> I have a system, that does most of what you are looking for.
>
> https://github.com/punchagan/blog-files
>
> Though it seems to be a little more complicated than it needs to be,
> it works for me and I haven't had the time and motivation to simplify
> it.
This is a commentary on the entire thread rather than on this specific
suggestion (though it's applicable here.)
All of these "take a git repo with text files in a lightweight markup
language (e.g. markdown, org, rst, etc.) and build a blog/website" tools
have this major flaw and there's no good solution:
They rebuild all pages in the site every time you update the site. Which
doesn't matter at all when you have 10 posts, but when you have a
hundred posts you notice the rebuild process, and by the time you have
1000-1500 posts, its totally unusable. Every time you fix a comma it
takes 1-3 minutes and nearly OOMs a VPS system to fix.
So what's the solution?
- Incremental builds
- Cached build elements.
- make-style dependency checking.
- indexes (for tags, archives, etc.) that are
The truth is that the part of the pipe that handles the filtering of the
text is important, but is not particularly central or crucial in the
grand scheme of the usability of this kind of application.
Cheers,
sam
--
tycho(ish) @
garen@tychoish.com
http://tychoish.com/
"don't get it right, get it written" -- james thurber
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-17 18:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 16:51 Minimal overhead Org-mode blogging system Karl Voit
2011-12-07 16:30 ` Steinar Bang
2011-12-07 17:20 ` Puneeth Chaganti
2011-12-07 20:11 ` Eric Schulte
2011-12-11 13:20 ` Bastien
2011-12-08 0:31 ` Karl Voit
2011-12-08 4:29 ` Puneeth Chaganti
2011-12-08 14:19 ` Karl Voit
2011-12-08 16:45 ` Puneeth Chaganti
2011-12-08 22:02 ` Karl Voit
2012-01-15 18:08 ` Steinar Bang
2012-01-16 22:54 ` Puneeth Chaganti
2012-01-19 22:15 ` Steinar Bang
2012-01-20 18:19 ` Chris Gray
2012-01-21 5:15 ` Scott Randby
2012-01-21 5:53 ` Nick Dokos
2012-01-21 6:26 ` Chris Gray
2012-01-17 18:50 ` tychoish [this message]
2012-01-18 3:06 ` Eric Schulte
2012-01-20 16:10 ` Bastien
2012-02-11 13:47 ` François Pinard
2011-12-11 4:33 ` Nathan Neff
2012-05-13 14:54 ` Neil Smithline
2012-05-15 2:24 ` Jude DaShiell
2012-05-16 0:48 ` Neil Smithline
2012-05-16 9:51 ` Jude DaShiell
2012-05-20 21:48 ` Neil Smithline
2012-06-17 8:09 ` Karl Voit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120117185029.GD8376@arendt.tychoish.net \
--to=garen@tychoish.com \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@karl-voit.at \
--cc=punchagan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).