[ckan-changes] commit/ckanext-disqus: dread: Renamed readme extension to show it is actually restructured text so it displays better in the bitbucket summary.

Bitbucket commits-noreply at bitbucket.org
Wed Jun 15 11:24:37 UTC 2011


1 new changeset in ckanext-disqus:

http://bitbucket.org/okfn/ckanext-disqus/changeset/4f82203d40b8/
changeset:   4f82203d40b8
user:        dread
date:        2011-06-15 13:24:17
summary:     Renamed readme extension to show it is actually restructured text so it displays better in the bitbucket summary.
affected #:  2 files (991 bytes)

--- a/README.md	Mon Dec 20 13:33:19 2010 +0100
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,29 +0,0 @@
-
-Disqus Plugin 
-=============
-
-The Disqus plugin allows site visitors to comment on individual 
-packages using an AJAX-based commenting system. The downsides of 
-this plugin are that comments are not stored locally and user 
-information is not shared between CKAN and the commenting system.
-
-Activating and Installing
--------------------------
-
-In order to set up the Disqus plugin, you first need to go to 
-disqus.com and set up a forum with your domain name. You will be 
-able to choose a forurm name. 
-
-To install the plugin, enter your virtualenv and load the source::
-
- (pyenv)$ pip install -e hg+https://bitbucket.org/okfn/ckanext-disqus#egg=ckanext-disqus
- 
-This will also register a plugin entry point, so you now should be 
-able to add the following to your CKAN .ini file:: 
-
- ckan.plugins = disqus <other-plugins>
- disqus.name = YOUR_DISQUS_NAME 
- 
-After clearing your cache and reloading the web server, comments 
-should now be available on package pages and on the home page. 
-

Repository URL: https://bitbucket.org/okfn/ckanext-disqus/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.




More information about the ckan-changes mailing list