| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Change example syntax on authorized_key module
* Change example syntax on cron module
* Change example syntax on group module
* Change example syntax on hostname module
* Change example syntax on seboolean module
* Change example syntax on selinux module
* Change example syntax on service module
* Change example syntax on sysctl module
* Change example syntax on systemd module
* Change example syntax on user module
* Change example syntax on debug module
* Change example syntax on fail module
* Change example syntax on include module
* Change example syntax on include_role module
* Change example syntax on include_vars module
* Change example syntax on pause module
* Change example syntax on wait_for module
* Change example syntax on apache2_module module
* > Change example syntax on django_manage module
* Change example syntax on htpasswd module
|
|
|
| |
Ignore blank lines in collectstatic output.
|
|
|
| |
there is no need to call out.split('\n') multiple times (line 275 and 277)
|
|\
| |
| | |
Remove 'cache_table' from required params
|
| |
| |
| |
| |
| |
| | |
Starting in Django 1.7, the createcachetable command looks for cache
table names in the CACHES settings dictionary, so cache_table is no
longer required, but is still allowed.
|
|/
|
|
|
| |
As of Ansible 2.x, invocation of Django's ```manage.py``` requires a valid "shebang". Additionally, ```manage.py``` must be executable.
The old invocation was hardcoded as ```python manage.py ...``` while the new invocation is ```./manage.py ...```. See [this PR](https://github.com/ansible/ansible-modules-core/pull/1165).
This change allows more flexibility for which Python interpreter is invoked, but breaks existing deployment when ```manage.py``` is not properly configured. This documentation update adds a note explaining the new requirements for ```manage.py```.
|
| |
|
|\
| |
| | |
make migrate command idempotent with django built-in migrations
|
| |
| |
| | |
Django since version 1.7 has built-in migrations, so no need to have south installed with recent django versions. The 'migrate' command works with built-in migrations without any change, but the output is different than the output produced by south, which breaks idempotence. This commit fixes this.
|
| | |
|
|\ \
| | |
| | | |
django_manage: Use shebang in manage.py instead of hardcoded "python"
|
| |/ |
|
|\ \
| | |
| | | |
Add example of using django_manage to run other commands.
|
| | | |
|
|\ \ \
| | | |
| | | | |
django_manage: expand ~ in app_path parameter
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow users to specify app_path parameters that contain ~, for example:
app_path=~/myproject
|
| |_|/
|/| | |
|
| |/
|/| |
|
|/
|
| |
Allow passing the database option to the django_manage module for migrations. This is usefull in situations where multiple databases are used by a django application.
|
|
|