A fork of the original bashblog unbound by some of the restrictions; but not too much.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
“PresGas” 3892aadcc6 Changed first couple of lines to reflect forking information. Slight modifications of global_variables in lines 25, 38, and 85 3 days ago
LICENSE Initial commit 2 weeks ago
Orig-BB-README.md Separated out original BB README file for posterity and began implementing rough sections of new README 1 week ago
README.md Separated out original BB README file for posterity and began implementing rough sections of new README 1 week ago
bb.sh Changed first couple of lines to reflect forking information. Slight modifications of global_variables in lines 25, 38, and 85 3 days ago

README.md

bashblog-unbound

A fork of the original bashblog unbound by some of the restrictions; but not too much.

Fork as of this point from GitHub:

c126913cdd

Usage

Download the code and copy bb.sh into a public folder (for example, $HOME/public_html/blog) and run

./bb.sh

This will show the available commands. If the file is not executable, type chmod +x bb.sh and retry.

Before creating your first post, you may want to configure the blog settings (title, author, etc). Read the Configuration section below for more information

To create your first post, just run:

./bb.sh post

It will try to use Markdown, if installed. To force HTML:

./bb.sh post -html

The script will handle the rest.

When you're done, access the public URL for that folder (e.g. http://server.com/~username/blog) and you should see the index file and a new page for that post!

Configuration

There are two ways to configure the blog strings:

  • Edit bb.sh and modify the variables in the global_variables() function
  • Create a .config file with your configuration values -- useful if you don't want to touch the script and be able to update it regularly with git

The software will load the values in the script first, then overwrite them with the values in the .config file. This means that you don't need to define all variables in the config file, only those which you need to override from the defaults.

The format of the .config file is just one variablename="value" per line, just like in the global_variables() function. Please remember: quote the values, do not declare a variable with the dollar sign, do not use spaces around the equal sign.

bashblog uses the $EDITOR environment value to open the text editor.