DESCRIPTION
        BULGE utilizes rc(1) and command line tools to display
        blog posts (blog), bookmarked URLs (url), or pastebin
        entries (paste). Tagging and RSS 2.0 feeds have been
        implemented.

SETUP
        To enable BULGE, add:

                conf_enable_bulge

        to _werc/config in the site root or appropriate sub-directory.

        To configure BULGE, copy or create the following files in
         _werc/bulge/, either in the site root or in the sub-directory
        you wish to activate (example files have been included in
        this distribution):

        _werc/bulge/config
                A list of variables that control various site options:

                        site_type=paste # blog, url, paste
                        site_tmp=_tmp
                        posts_per_page=10
                        show_body=1
                        show_date=1
                        show_footer=0
                        show_header=0
                        show_id=1
                        show_link=0
                        show_raw=1
                        show_sidebar=0
                        show_tags=0
                        show_title=1

        _werc/bulge/footer
                HTML or markdown that will appear as the foot of
                the BULGE content area.

        _werc/bulge/header
                HTML or markdown that will appear at the head of
                the BULGE content area.

        _werc/bulge/sidebar
                HTML or markdown that will appear on one side of
                the BULGE content area.

        Finally, sample stylesheets are provided in the directory
        pub/. Copy any of these to _werc/pub/style.css to try
        them out.

POSTS
        Posts are stored in the directory src/ relative to the
        site root or active sub-directory.

        Directory names in src/ that do not match the regular
        expression ^[0-9]*$ will not be included in the listing of
        posts that are displayed in the browser. However, such
        directories will still be accessible when called directly
        via the appropriate URL.

        A post's directory contains the following files and
        directories (an example post's directory has been
        included in this distribution):

                body
                date
                link
                tags/
                title

        The tags/ directory contains one empty file named
        for each tag associated with the post.

ADMIN
        Any tool that can create, alter, or delete flat files
        and directories is sufficient to administer a BULGE.

        Web-based login and administration utilizes werc's
        user authentication combined with custom pages
        for adding, updating and deleting posts:

        http://$masterSite/login
                Login using werc's user authentation.

        http://$masterSite/user
                After logging in, manage posts through the
                admin interface.

        Web-based administration requires that the src/
        directory and its sub-directories are writable by
        the web server process.

SOURCE
        http://plan9.stanleylieber.com/werc/apps/bulge.tgz

DEVELOPMENT SITES
        blog
                http://stanleylieber.com
        bookmarks
                http://url.stanleylieber.com
        pastebin
                http://okturing.com

LICENSE
        Some code was borrowed from the existing blagh
        app, while other code was adapted from a previous
        project. In all cases, the code is released to the
        public domain.

Didn't you already post this app, but with a different name?

I recently posted a utility for BULGE called fg that imports an RSS
feed and converts it to BULGE posts (now included in the distribution).

The whole thing is loosely based on my previous, non-werc project,
askeladd:

http://code.stanleylieber.com/askeladd

-sl

The example CSS stylesheets are kind of a mess, as I haven't
yet removed a lot of deprecated items. But they work.

-sl

Check the bottom of the first post...
On Aug 30, 2011 3:19 PM, "David J Patrick" <d...@linuxcaffe.ca> wrote: