Packaging Stand-Alone Django Apps: Difference between revisions

From Littledamien Wiki
Jump to navigation Jump to search
Line 6: Line 6:
Try to avoid naming conflicts, of course. (Check resources like PyPI.)
Try to avoid naming conflicts, of course. (Check resources like PyPI.)


* Create `README.rst`
* Create `README.md`
** In the package root, e.g. `littled-addresses/README.rst`.
** In the package root, e.g. `littled-addresses/README.md`.
** Sample contents at [https://docs.djangoproject.com/en/1.7/intro/reusable-apps/#packaging-your-app How to Write Reusable Apps—Packaging your app]
** Sample contents at [https://docs.djangoproject.com/en/1.7/intro/reusable-apps/#packaging-your-app How to Write Reusable Apps—Packaging your app]
* Create `LICENSE` file in the package root.  
* Create `LICENSE` file in the package root.  

Revision as of 14:00, 15 February 2016

Directory structure

The app goes in a directory outside of any Django web project. If the app is addresses, structure it littled-addresses/addresses/.[1]

Try to avoid naming conflicts, of course. (Check resources like PyPI.)

Building the package

Before committing changes to the package, make sure to update the version if needed.
|
 +- [package_root]
      |
      +- [package_dir]
      |    |
      |    +- __init__.py > __version__
      | 
      +- [...]
      |
      +- setup.py > setup.version

Command to build the package:

$ python setup.py sdist
  • Run from the package root directory.
  • Creates a dist directory which contains the (zipped) package.

Using the package

Follow the instructions for upgrading the package if the package has already been installed.

Installing the package

Push the package distribution to GitHub.

Add the package and version to requirements.txt in the project's root directory:

-e git://github.com/account_name/package_repo.git#egg=package_name

Replacing account_name, package_repo, and package_name in the URL with the appropriate values.

Install the package with pip. (Make sure that the project's virtual environment has been activated first.)

$ pip install -r requirements.txt

Upgrading the package

Update the version number in requirements.txt.

Run pip install -r requirements.txt

Using the package in a project

Assuming that the package is

|- django-addresses
|   |
|   |- addresses
|   |   |
|   |   `-- [...]
|   |
|   `-- [...]
|
`-- [...]

In the project's settings.py:

INSTALLED_APPS = (
        ...
        'addresses',
    )

Then from the web project root:

$ python manage.py makemigrations addresses
$ python manage.py migrate addresses

To reference the objects in a model within the web project:

class Person(models.Model):
    address = models.ForeignKey('addresses.Address')
    # ...

Resetting migrations

In the case that migrations have been made, and you want to rebuild the database objects from scratch:

$ python manage.py migrate --fake addresses zero
$ python manage.py migrate addresses
  • The first command sets the migration counter to before the initial (0001) migration.
  • The 2nd command migrates the models at the state of the latest migration.[2]

Uninstalling the package

$ pip uninstall django-addresses

Uninstalling a stand-along package will remove the migrations for that package. Without the migrations, Django projects won't be able to sync to any changes to the app's models. It's better to upgrade than to uninstall and install.[3]

Notes

  1. How to Write Reusable Apps (Django documentation)
  2. How to reset migrations in Django 1.7? (Stackoverflow)
  3. Migrations (Django documentation)