Required settings¶

Modify your projects settings.py file following the next steps:

In INSTALLED_APPS:

'pagination',
'tagging',
'planet',

Be sure to set the site id:

SITE_ID = 1

Include the context processor:

TEMPLATE_CONTEXT_PROCESSORS = (
    #...
    'planet.context_processors.context',
)

Add the pagination middleware:

MIDDLEWARE_CLASSES = (
    # ...
    'pagination.middleware.PaginationMiddleware',
)

Urls¶

In urls.py:

urlpatterns = patterns('',
    # ...
    url(r'^planet/', include('planet.urls')),
)

Optional settings¶

# To modify cookie names so you don’t have login conflicts with other projects
LANGUAGE_COOKIE_NAME = "myplanetlng"
SESSION_COOKIE_NAME = "myplanetid"
# user agent
PLANET_USER_AGENT = "Django Planet"
# limit the number of posts to be retrieved by feed (default is 30)
PLANET_MAX_POSTS = 20
# base template to be used (base.html is the default)
PLANET_BASE_TEMPLATE ="my_base.html"

Select the async backend:

ASYNC_BACKEND = "huey"

This will be detailed in the next section.

Cron job¶

30 * * * * python manage.py planet_update_all_feeds

This attempts to pull in new posts every 30 minutes.

Celery¶

Install Celery pip install celery redis. You will need a celery.py file as explained here. A Redis or RabbitMQ instance is also required, check the Celery docs. In settings.py:

    PLANET_ASYNC_BACKEND = "celery"

from datetime import timedelta
    CELERYBEAT_SCHEDULE = {
        'update-feeds': {
            'task': 'planet.tasks.update_feeds',
            'schedule': timedelta(minutes=30),
        },
    }

Then launch the worker: start a beat and a worker:

celery -A project_name beat  -l info --broker='redis://localhost:6379/0'
celery -A project_name worker  -l info --broker='redis://localhost:6379/0'

Huey¶

Huey is easier to configure than Celery. If you are not familiar with Celery you might want to use it for an easy start.

Install Huey: pip install huey. Add huey.contrib.djhuey in INSTALLED_APPS. In settings.py:

PLANET_ASYNC_BACKEND = "huey"

from huey import RedisHuey
HUEY = RedisHuey('your_project_name')

Launch the worker:

python manage.py run_huey

Index page¶

Post view¶

Tag view¶

Philosophy¶

• django-planet is BSD-licensed. All contributed code must be either
  • the original work of the author, contributed under the BSD, or...
  • work taken from another project released under a BSD-compatible license.
• GPL’d (or similar) works are not eligible for inclusion.
• django-planet’s git master branch should always be stable, production-ready & passing all tests.

Guidelines For Reporting An Issue/Feature¶

So you’ve found a bug or have a great idea for a feature. Here’s the steps you should take to help get it added/fixed in Tastypie:

• First, check to see if there’s an existing issue/pull request for the bug/feature. All issues are at https://github.com/matagus/django-planet/issues and pull reqs are at https://github.com/matagus/django-planet/pulls.
• If there isn’t one there, please file an issue. The ideal report includes:
  • A description of the problem/suggestion.
  • How to recreate the bug.
  • If relevant, including the versions of your:
    • Python interpreter
    • Django
    • django-planet
    • Optionally of the other dependencies involved
  • Ideally, creating a pull request with a (failing) test case demonstrating what’s wrong. This makes it easy for us to reproduce & fix the problem. Instructions for running the tests are at Django Planet

Guidelines For Contributing Code¶

If you’re ready to take the plunge & contribute back some code/docs, the process should look like:

• Fork the project on GitHub into your own account.
• Clone your copy of django-planet.
• Make a new branch in git & commit your changes there.
• Push your new branch up to GitHub.
• Again, ensure there isn’t already an issue or pull request out there on it. If there is & you feel you have a better fix, please take note of the issue number & mention it in your pull request.
• Create a new pull request (based on your branch), including what the problem/feature is, versions of your software & referencing any related issues/pull requests.

In order to be merged into django-planet, contributions must have the following:

• A solid patch that:
  • is clear.
  • works across all supported versions of Python/Django.
  • follows the existing style of the code base (mostly PEP-8).
  • comments included as needed.
• A test case that demonstrates the previous flaw that now passes with the included patch.
• If it adds/changes a public API, it must also include documentation for those changes.
• Must be appropriately licensed (see “Philosophy”).
• Adds yourself to the AUTHORS file.

If your contribution lacks any of these things, they will have to be added by a core contributor before being merged into django-planet proper, which may take substantial time for the all-volunteer team to get to.

Guidelines For Core Contributors¶

If you’ve been granted the commit bit, here’s how to shepherd the changes in:

• Any time you go to work on djano-planet, please use git pull --rebase to fetch the latest changes.

• Any new features/bug fixes must meet the above guidelines for contributing code (solid patch/tests passing/docs included).

• Commits are typically cherry-picked onto a branch off master.

  • This is done so as not to include extraneous commits, as some people submit pull reqs based on their git master that has other things applied to it.

• A set of commits should be squashed down to a single commit.

  • git merge --squash is a good tool for performing this, as is git rebase -i HEAD~N.
  • This is done to prevent anyone using the git repo from accidently pulling work-in-progress commits.

• Commit messages should use past tense, describe what changed & thank anyone involved.

  “”“Added template tag to get all posts.

  Further description appears here if the change warrants an explanation as to why it was done.”“”

• For any patches applied from a contributor, please ensure their name appears in the AUTHORS file.

• When closing issues or pull requests, please reference the SHA in the closing message (i.e. Thanks! Fixed in SHA: 6b93f6). GitHub will automatically link to it.