A static site generator, powers marcyes.com
You run bang from the command line:
$ bang command --project-dir=...
1 minute getting started
First, install bang:
$ pip install bang
Make a new project:
$ bang generate --project-dir=~/bang-quickstart
Then compile your new project:
$ bang compile --project-dir=~/bang-quickstart
And start up the development server to take a look at your new project:
$ bang serve --project-dir=~/bang-quickstart
Now, open a browser and load
localhost:8000 to see your masterpiece, that's it!
Setup and Configuration
A bang site can have any folder structure and bang will check each folder for a markdown (extension
.md) file, if it finds one named
index.md it will not treat it like a blog post but just compile the folder to an
index.html file. If it finds a markdown file with any other name, then it is considered a blog post with the file's name being the title. So, if you have this file structure:
project-dir/ input/ 2014/ 001-this-is-the-slug/ This is the title of the blog post.md
It would compile down to a blog post with a title This is the title of the blog post available at the uri:
Any other files (images or whatnot) will just be copied over to their respective locations.
Your project directory is where all the magic happens. It has to contain a few folders:
This is where everything you want to be in the final output folder should go, this includes your blog posts and any other files/folders you want your live static site to contain.
This is where all your Jinja templates go, they are used to compile your blog posts to their final form. Bang looks for a few template files by default for blog posts:
post.html- This contains the html for rendering a post's permalink page.
posts.html- This contains the html for rendering a list of posts.
This is the default output directory when the
compile command is used with no
You can add this file to configure bang when compiling:
# /project_dir/bangfile.py name = "your site name" description = "your site description" host = "example.com"
If you don't want to bother with a
bangfile.py in your project directory, Bang can also be configured using environment variables, basically, any
BANG_* environment variables wil be put into the configuration, here are a couple you might want to set:
- BANG_HOST -- the host of your website, this is used to generate urls and stuff.
- BANG_METHOD -- the http method to use (either
You can also combine a bangfile with the environment, this makes it easy to have different environments:
# /project_dir/bangfile.py import os name = "your site name" description = "your site description" # change the host and scheme based on the environment env = os.environ.get("BANG_ENV", "prod") if env == "prod": host = "example.com" scheme = "https" else: host = "localhost" scheme = "http"
For the most part, Bang uses vanilla markdown, but there are some enhancements you can take advantage of if you like:
^n footnote will just assign footnotes in order:
first[^n] second[^n] [^n]: this will be assigned to the "first" footnote [^n]: this will be assigned to the "second" footnote
That way you don't have to worry about uniquely naming footnotes since they are just assigned in order, but if you want to give your footnotes unique names that works also.
Similar to the footnotes, using the
n reference name:
[first][n] [second][n] [n]: http://first.com [n]: http://second.com
If no title is used, then the alt becomes the title:
![this will be the title](path/to/image.jpg)
bang includes a couple built-in plugins that you can include in your
bangfile.py, to activate them per site:
# /project_dir/bangfile.py from bang.plugins import sitemap # to automatically generate a sitemap.xml file from bang.plugins import feed # generate an rss feed at host/feed.rss for the last 10 posts
That's it, once they are imported they will run when they need to.
Use this to compile your
project-dir/input directory to the final form in the
Compile your site using the default output directory:
$ bang compile --project-dir=...
That will place the compiled output to
project-dir/output, you can also move the output directory to another location:
$ bang compile --project-dir=... --output-dir=...
Use this to fire up a local server so you can see your compiled site. You can set the port with the
$ bang server --project-dir=... --port=8000
This is designed to be used on the remote server that will host your site in a cron job, it will try and pull down the code using a git repo, if there are changes, then it will compile the new changes, since it is run in cron, you should include the full path:
$ /usr/local/bin/bang watch --project-dir=...
Generate a site skeleton that you can use as a starting point to your own bang site, this will take the
project_dir and make sure it exists (or create it) and then add
template dirs along with skeleton template files.
$ bang generate --project-dir=...
Events are callbacks that are fired at specific times.
The easiest way to hook these in to your site compiling is to define or import them into your
bangfile.py configuration file. You can see examples of how they are used in the
Events are basically defined like this:
from .. import event, echo @event.bind("output.finish") def callback(event_name, site): """print all the post titles and urls to the screen""" for p in site.posts: echo.out(p.title) echo.err(p.url) # alternative register call: event.listen('output.finish', callback)
This event is fired after all the posts are compiled, right now it is used to do things like generating RSS feeds and the sitemap.
This event is fired for every element in a post that matches, so if you wanted to do something with
a tags, you could hook up a callback to listen on
from .. import event, echo @event.bind("dom.a") def callback(event_name, parent, elem): """print all href urls in every a tag""" echo.out(elem.href)
Anytime the configuration context changes, this event is called, when the html pages are generated,
context.web is the broadcast event, the feed plugin will broacast
context.feed and the sitemap plugin will broadcast
from .. import event @event.bind("context.web") def callback(event_name, config): """allows custom configuration for web context""" pass
If you cloned this repo, you can test out bang by running (from the repo working directory:
$ python -m bang generate -d /path/to/testsite/ $ python -m bang compile -d /path/to/testsite/ $ python -m bang serve -d /path/to/testsite/
You can also run the unit tests:
$ python -m unittest bang_test
pip install bangtext