- Admin interface, with support for (unpublished) draft posts and draft versions
- Anti-spam protection on comments via Akismet
- Assets stored on Amazon S3
- Avatars on comments pulled from Gravatar
- Apps built with this engine can easily be hosted on Heroku
- Email notifications
- Atom feeds for posts and comments
- Highly customisable
This app makes use of MarkItUp.
Copyright (c) 2011 Michael Patricios. See mit-license.txt for details.
Create a new rails app:
rails new badass-demo
Edit the gemfile and add the badass gem:
gem 'badass', :git => 'git://github.com/mpatric/badass.git', :branch => 'master'
Make sure you have bundler installed (with sudo if you're not using rvm):
gem install bundler
Run the badass generator:
rails g badass:site -f
Update database.yml as appropriate, then create your database and run the migrations:
rake db:create rake db:migrate
If you wish to generate some test data, run:
Start rails locally:
Go to http://localhost:3000/admin with your web browser for the admin interface, if you've generated test data login with test/test
Go to http://localhost:3000/ with your web browser for the blog
Edit the configuration file config/badass.yml. The keys are fairly self-explanatory. If you want to use Akismet for spam protection you will need to register at akismet.com and get an API key. If you want to track analytics with google analytics you will need your analytics account id (the number starting 'UA-').
Edit the Amazon s3 configuration in config/s3.yml to include your access key id and secret access key. You will need to sign up for Amazon web services to use this. You won't be able to upload assets to your blog without setting up s3 support.
You should probably add password_confirmation to the list of filtered parameters in config/application.rb:
config.filter_parameters += [:password, :password_confirmation]
If you are setting up a personal blog, you'll probably want to leave max_users for production in badass.yml on 1, which means as soon as you register yourself it won't be possible for other people to register on your site. If you're setting up a blog for multiple people to use, you might want to increase this number.
If you want some information to appear on the top-right of the page (typically information about yourself), edit the partial /app/views/home/_about.html.haml
You can replace any of the views provided by the engine by providing the same view in your app. The easiest way to do this is to copy a view from the app/views folder in the badass gem to the same path in your project, then edit yours.
You are provided with three sass stylesheets in public/stylesheets/sass:
- admin.sass - styles for the admin interface
- site.sass - styles for the public blog site
- content.sass - styles for the content, primarily for the public blog site, but also used in the admin interface for previewing posts
Each of these stylesheets pulls in the default styles from the badass gem. You can easily over-ride any of the styles in the application by entering styles into these three stylesheets. Do not remove the import statements at the start of each stylesheet, or you will lose all the default styling.
As of version 0.2, the author of a post can get email notifications when comments are made to their posts. In order to enable this functionality, ensure these two keys are set in your badass.yml file (with an appropriate email address):
email_enabled: true email_sender: 'email@example.com'
Then make sure you set up the smtp settings for action mailer (usually in config/environment/production.rb). If you are using gmail, these are the settings:
config.action_mailer.smtp_settings[:address] = 'smtp.gmail.com' config.action_mailer.smtp_settings[:port] = 587 config.action_mailer.smtp_settings[:domain] = ('gmail.com' or your domain if you have a custom gmail domain) config.action_mailer.smtp_settings[:user_name] = (full username, e.g. 'firstname.lastname@example.org' or 'email@example.com') config.action_mailer.smtp_settings[:password] = (password) config.action_mailer.smtp_settings[:authentication] = 'plain' config.action_mailer.smtp_settings[:enable_starttls_auto] = true
Update your gems with bundler:
It is strongly recommended that the generator is re-run whenever the badass gem is updated, as files generated with the site generator may have changed too. Run:
rails g badass:site -s
That will re-run the site generator, but skip the files you have modified so they don't get over-written. If any new migrations are generated by this you will need to run the migrations:
Things that might be added in the future:
- More semantic markup
- Auto sitemap generation
- Additional 'themes' out of the box
- Validate email address on comment entry
- Email followup comments to other commenters, with unsubscribe functionality