dj
==
**dj** is a command line tool that makes [Django][1] development *even* simpler. It provides shortcuts for most common [manage.py][2] commands.
It uses [virtualenv][3] and [South][4] by default.
Creating New Project
--------------------
$ dj new myproject/
New python executable in myproject/bin/python
Installing Setuptools...
...
$ cd myproject/
$ ls -l
total 0
drwxr-xr-x 14 user wheel 476 Nov 15 15:48 bin
drwxr-xr-x 3 user wheel 102 Nov 15 15:47 include
drwxr-xr-x 3 user wheel 102 Nov 15 15:47 lib
drwxr-xr-x 6 user wheel 204 Nov 15 15:50 myproject
Adding New Applications
-----------------------
$ dj app example
Creating migrations directory at '/../myproject/example/migrations'...
Creating __init__.py in '/../myproject/example/migrations'...
Created 0001_initial.py. You can now apply this migration with: ./manage.py migrate example
Running migrations for example:
- Migrating forwards to 0001_initial.
> example:0001_initial
- Loading initial data for example.
Installed 0 object(s) from 0 fixture(s)
This will also update *settings.py* file.
Schema Migration After Model Update
-----------------------------------
$ vim myproject/example/models.py
$ dj sync example
+ Added model example.Person
Created 0002_auto__add_person.py. You can now apply this migration with: ./manage.py migrate example
Running migrations for example:
- Migrating forwards to 0002_auto__add_person.
> example:0002_auto__add_person
- Loading initial data for example.
Installed 0 object(s) from 0 fixture(s)
Shell & Test Server
-------------------
$ dj shell
$ dj run
Validating models...
0 errors found
November 15, 2013 - 14:10:00
Django version 1.6, using settings 'myproject.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
Installing Packages Inside Virtual Environment
----------------------------------------------
$ dj install Celery
Downloading/unpacking Celery
...
Issues / To Do
--------------
* Using bash scripts inside Python, will fix that.
* Argument parser needs to be replaced.
* Deleting applications should be handled manually.
Reporting Bugs, Submiting Pull/Feature Requests
-----------------------------------------------
Feel free to report any bugs, submit pull requests and ask for feature requests.
[1]: https://www.djangoproject.com/
[2]: https://docs.djangoproject.com/en/dev/ref/django-admin/
[3]: http://virtualenv.org
[4]: http://south.aeracode.org
Metadata
Release files for dj-cli 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dj-cli-0.2.tar.gz | 3.0 kB | Without provenance | Details |
Release files / dj-cli-0.2.tar.gz
| Download URL | dj-cli-0.2.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d68fec0277d5283b9eb7a0b9234b394674c97477e6435ba3f6789e4a86114411
|
|
BLAKE2b-256 checksum How to use checksums |
9111378e50bded05dff0db3c56981c55125163fcd473a0affad0d08d7a3dd0a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dj-cli 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.