Skip to content
This repository

Monologue is a basic blogging engine. It is a Rails mountable engine you can mount in your already existing Rails app, or a in a new one! Enjoy.

Fetching latest commit…

Cannot retrieve the latest commit at this time

README.md

Monologue

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.

Gem Version Build Status Code Climate Coverage Status

IMPORTANT: version

This README is for Monologue 0.3.X.

Upgrade and changes

To know how to upgrade, see UPGRADE.md file. If you want to know what changed since the last versions, see CHANGELOG.md.

Questions? Problems? Documentation?

Here are a few features

  • Rails mountable engine (fully named spaced and mountable in an already existing app)
  • tested
  • back to basics: few features
  • tags (or categories)
  • RSS
  • 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 [monologue-markdown](https://github.com/jipiboily/monologue-markdown) extension

missing features

Installation

1. Add the gem to your Gemfile

gem "monologue"

And run bundle install to fetch the gem and update your 'Gemfile.lock'.

2. Route to Monologue

Add this to your route file (config/route.rb)

# 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 /blog/monologue. Here we decide to use monologue as default route mounting it at /, it means that the admin section will directly be available at /monologue.

3. Migrate Monologue's database tables

Run these commands:

  1. $bundle exec rake monologue:install:migrations
  2. $bundle exec rake db:create (only if this is a new project)
  3. $bundle exec rake db:migrate

4. Create a user

Open your development console with rails c, then:

Monologue::User.create(name: "monologue", email:"monologue@example.com", 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.

6. Ready

Start your server and head on http://localhost:3000/monologue to log in the admin section.

Note to Heroku users

  1. Additionnal step: turn caching off in config/environments/production.rb:
config.action_controller.perform_caching = false
  1. 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

Enable caching

See full caching doc here.

Customization

See the Wiki - Customizations.

Requirements

  • Rails 3.1 +
  • Database: MySQL & Postgres are supported but other databases might work too.

Authors

Contribute

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:

Thanks to

Zurb for the "social foundicons".

Something went wrong with that request. Please try again.