Monologue is a basic mountable blogging engine in Rails built to be easily mounted in an already existing Rails app, but it can also be used alone.
This README is for Monologue 0.3.X.
Upgrade and changes
Questions? Problems? Documentation?
Here are a few features
- Rails mountable engine (fully named spaced and mountable in an already existing app)
- back to basics: few features
- tags (or categories)
- multiple users
- support for Google Analytics and Gaug.es tags
- few external dependencies (no Devise or Sorcery, etc…) so we don't face problem integrating with existing Rails app.(Rails mountable engines: dependency nightmare?)
- comments are handled by disqus
- enforcing Rails cache for better performance (only support file store for now). Read this to enable it.
more in the CHANGELOG
bonus: there is a
- see roadmap!
1. Add the gem to your
bundle install to fetch the gem and update your 'Gemfile.lock'.
2. Route to Monologue
Add this to your route file (
# This line mounts Monologue's routes at the root of your application. # This means, any requests to URLs such as /my-post, will go to Monologue::PostsController. # If you would like to change where this engine is mounted, simply change the :at option to something different. # # We ask that you don't use the :as option here, as Monologue relies on it being the default of "monologue" mount Monologue::Engine, at: '/' # or whatever path, be it "/blog" or "/monologue"
For example, if you decide to mount it at
/blog, the admin section will be available at
Here we decide to use monologue as default route mounting it at
/, it means that the admin section will directly
be available at
3. Migrate Monologue's database tables
Run these commands:
bundle exec rake monologue:install:migrations
bundle exec rake db:create(only if this is a new project)
bundle exec rake db:migrate
4. Create a user
Open your development console with
rails c, then:
Monologue::User.create(name: "monologue", email:"firstname.lastname@example.org", password:"my-password", password_confirmation: "my-password")
5. Configure Monologue.
This is all done in an initializer file, say
config/initializers/monologue.rb. More on this in the Wiki - Configuration.
Start your server and head on http://localhost:3000/monologue to log in the admin section.
Note to Heroku users
- Additionnal step: turn caching off in
config.action_controller.perform_caching = false
- If you use compiled assets, I recommend you to add
gem "tinymce-rails"to your Gemfile otherwise you might not be able to post an article.
Note to users
Monologue is using his own tables. If you want to use your own tables with monologue (for example the User table) this might help you to monkey patch Monkey Patch
See the Wiki - Customizations.
- Rails 3.1 +
- Database: MySQL & Postgres are supported but other databases might work too.
Fork it, then pull request. Please add tests for your feature or bug fix.
You will need to install this before running the test suite:
Zurb for the "social foundicons".