Various issues with the settings "module"

Bug #1289892 reported by David Fischer on 2014-03-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-django (Juju Charms Collection)
Undecided
Patrick Hetu

Bug Description

Hello,

I am trying to deploy my own Django project with this promising charm however I am unable to find the right configuration (config.yaml) to make it work. My problem is related to the structure of my site, created with django-admin.py from Django 1.7+

django-admin.py startproject project
~/project$ tree .
.
├── manage.py
└── project
    ├── __init__.py
    ├── settings.py
    ├── urls.py
    └── wsgi.py

As you can see manage.py is the only file in the site directory, the other files of the project are stored into a sub-directory.

It is why, after 2 hour of configuration tweaking & testing, I am still not able to configure the charm according this structure.

For my project the case is even more complicated because I created a directory settings/ containing :

~/my_complicated_project$ tree .
...
├── my_complicated_project
│   ├── __init__.py
│   ├── settings
│   │   ├── base.py
│   │   ├── __init__.py
│   │   └── srv204.py
│   ├── urls.py
│   └── wsgi.py

Of course this works flawless when running my site locally ...

Bonus question : The option "requirements_apt_files" in config.yaml seem not used at all.

Changed in python-django (Juju Charms Collection):
assignee: nobody → Patrick Hetu (patrick-hetu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers