From e4342b7d28d3b0c470954f60a02340b472abe7c0 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Wed, 5 Sep 2007 14:01:31 +0000 Subject: Refs #5343 -- Reverted [6047]. Loading custom commands was causing the settings file to get read before the options could be processed to determine if a --settings option was present. Back to the drawing board (again)... git-svn-id: http://code.djangoproject.com/svn/django/trunk@6050 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/django-admin.txt | 29 ----------------------------- 1 file changed, 29 deletions(-) (limited to 'docs') diff --git a/docs/django-admin.txt b/docs/django-admin.txt index e929f13109..e3d1067dd3 100644 --- a/docs/django-admin.txt +++ b/docs/django-admin.txt @@ -619,32 +619,3 @@ distribution. It enables tab-completion of ``django-admin.py`` and * Press [TAB] to see all available options. * Type ``sql``, then [TAB], to see all available options whose names start with ``sql``. - -Customized actions -================== - -**New in Django development version** - -If you want to add an action of your own to ``manage.py``, you can. -Simply add a ``management/commands`` directory to your application. -Each python module in that directory will be discovered and registered as -a command that can be executed as an action when you run ``manage.py``:: - - /fancy_blog - __init__.py - models.py - /management - __init__.py - /commands - __init__.py - explode.py - views.py - -In this example, ``explode`` command will be made available to any project -that includes the ``fancy_blog`` application in ``settings.INSTALLED_APPS``. - -The ``explode.py`` module has only one requirement -- it must define a class -called ``Command`` that extends ``django.core.management.base.BaseCommand``. - -For more details on how to define your own commands, look at the code for the -existing ``django-admin.py`` commands, in ``/django/core/management/commands``. -- cgit v1.3