- Globally, now do word splitting (IFS) only on newline (which also makes "$*" expand with newline separator instead of space). - Disable globbing (pathmame expansion), to be re-enabled locally using 'set +f' where needed (typically in a subshell). These changes help eliminate unexpected snags and security vulnerabilities in case someone forgets to quote a variable somewhere. They should also make the code "just work" with spaces and other special characters in file names and tags (as long as they're not newline characters, but that can't happen with regular use of the script as the newline is the separator). This means that, as of this change, editing or completely emptying the convert_filename filter should no longer pose any problems as far as bb.sh is concerned. The changes to adapt the code to the above are mainly: - Now that we do word splitting on newline only, we can go back to iterating through files in a "for" loop instead of using "read" with a here-document, which is more readable. However, to enable globbing locally, a technique adaptation is needed, like: for file in $(set +f; printf '%s\n' *.html) or for file in $(set +f; ls -t -- *.html) # sort by date, newest first Given IFS=$'\n' and globbing disabled globally, this technique is robust for all special characters in file names except for newlines. - invoke_editor() function replaces direct $EDITOR calls, because we need to locally word-split $EDITOR on spaces in case it contains arguments. - parse_file(): rewrite tag parsing to handle possible spaces in tags - tags_in_post(): output line-separated instead of space-separated tags; further adjust sed script to handle possible spaces in tags - rebuild_tags(): this function was refactored to use an array internally. Instead of two combined strings, it now takes HTML files and tags as separate arguments, separated by a single "--tag" argument. This allows for spaces and other special characters in both file names and tags. (See also commit
|5 years ago|
|README.md||6 years ago|
|bb.sh||5 years ago|
A single Bash script to create blogs.
I created it because I wanted a very, very simple way to post entries to a blog by using a public folder on my server, without any special requirements and dependencies. Works on GNU/Linux, OSX and BSD.
How simple? Just type
./bb.sh post and start writing your blogpost.
You can see it live here: read the initial blog post. That page was 100% generated using bashblog, no additional tweaking.
Download the code and copy bb.sh into a public folder (for example,
$HOME/public_html/blog) and run
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:
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.
and you should see the index file and a new page for that post!
bb.shand start blogging.
coreutilson a Mac. It does some magic to autodetect which command switches it needs to run depending on your system.
ftpfsand run this script locally
Configuration is not required for a test drive, but if you plan on running your blog with bashblog, you will want to change the default titles, author names, etc, to match your own.
There are two ways to configure the blog strings:
bb.shand modify the variables in the
.configfile 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
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
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.
Read the Changelog section for more updates or check out the news on my blog
Bashblog started at 500 SLOC and it now has hit the 1000 SLOC barrier. If we want to keep the code minimal and understandable, we need to make the difficult effort to restrain ourselves from adding too many features.
All bugfixes are welcome, but brand new features need to be strongly justified to get into the main tree. Every new request will be honestly and civilly discussed on the comments. As a guideline, pull requests should:
.configfor each one
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.