davidhalter / depl Goto Github PK

Most of my Django projects have the following structure:

README.rst
requirements.txt
depl.yml  # In the future?
myproj/
    manage.py
    conf/
    front/

Currently depl does not seem to support that. I added a way to customize the path to the manage.py module in dbrgn@e0f9c25. But then deployment still fails, because the autodetected settings file is imported from the root directory.

Another approach would be to put the depl file in the myproj directory, but then the requirements.txt file wouldn't be found anymore. And platforms like Heroku require the requirements file to be in the git root.

I thought about configuring a project_dir, which would then point to the myproj directory. Additionally, you would need a requirements_file config variable, to support requirements files in arbitrary directories

Then you could simply copy the requirements file as well as the project directory to the remote server...

When defining django before postgresql in depl.yml, things don't work. There should be a way to declare dependencies, so that the order of declaration doesn't matter.