<commit_before>= governor_livejournal

Description goes here.

== Contributing to governor_livejournal
 
* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
* Fork the project
* Start a feature/bugfix branch
* Commit and push until you are happy with your contribution
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.<commit_msg>fleshed out readme<commit_after>= governor_livejournal

<b>Governor[http://carpeliam.github.com/governor/]</b> (named after <NAME>) is the pluggable blogging platform for Rails, built for people
who want to build their blog into their website, not build their website into
their blog.

*governor_livejournal* is a plugin for Governor, allowing you to cross-post your
articles to LiveJournal[http://www.livejournal.com].

== Dependencies

* Governor[http://carpeliam.github.com/governor/]
* GovernorBackground[https://github.com/carpeliam/governor_background]
* The livejournal[https://github.com/carpeliam/livejournal] gem (my fork fixes
  a small bug, hopefully soon you'll be able to use the main repo)
* And because of the GovernorBackground dependency, either
  Delayed_Job[https://github.com/collectiveidea/delayed_job] or
  Resque[https://github.com/defunkt/resque]. If you use Resque, it's highly
  recommended that you use
  resque-status[https://github.com/quirkey/resque-status] as well.

== Setting up

First, install the above dependencies. Then, in your Gemfile, add the
following:

    gem 'governor_livejournal'

Once you've installed the gem into your app, you need to run the generator:

    rails generate governor:add_livejournal [RESOURCE]

This will add a migration for associating articles to livejournal posts as
well as an initializer in which you'll need to set your username and password
for livejournal.

== Contributing to governor_livejournal
 
* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
* Fork the project
* Start a feature/bugfix branch
* Commit and push until you are happy with your contribution
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
{'fraction_non_alphanumeric': 0.06395112016293279, 'fraction_numerical': 0.0, 'mean_word_length': 4.765258215962441, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 6, 'https://': 5, 'lorem ipsum': 0, 'www.': 1, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2516593', 'n_tokens_mistral': 673, 'n_tokens_neox': 647, 'n_words': 311}