The computer should be doing step 6

[danreeves]

Move the contents of the new [projectname] folder out into the root

This is because we run wagtail start [name] instead of wagtail start [name] .. This complains about the requirements.txt already existing.

We should script this or something

[mjdavies]

Like the look of this, but having a lot of ball ache with the "Move the contents of the new [projectname] folder out into the root".

+1 for having the computer do this element.

What should the final requirements.txt look like, and where should it be?

[danreeves]

Hi @mjdavies

The final requirements.txt should look like the one in this repo, with anything else you want added. I suppose you could use the one generated by wagtail start [name] . but I don't remember right now what's in it and what's missing.

The requirements.txt file should be at the root of your project alongside manage.py

[mjdavies]

Cheers Dan

The requirements.txt that wagtail start creates has these values

Django>=1.9,<1.10
wagtail==1.3.1

wagtail1.3.1 has these dependencies by the looks

beautifulsoup4 (4.4.1)
django-appconf (1.0.1)
django-compressor (2.0)
django-modelcluster (1.1)
django-taggit (0.18.0)
django-treebeard (3.0)
djangorestframework (3.3.2)
html5lib (0.9999999)
Pillow (3.1.1)
pytz (2015.7)
rcssmin (1.0.6)
rjsmin (1.0.12)
six (1.10.0)
Unidecode (0.4.19)
Willow (0.2.2)

I've always struggled a bit working out what needs to be in a production level requirements.txt. We end up copying them from other projects alot, but I've got a sneaky feeling we're including some modules that aren't needed sometimes.

Be nice if torchbox would release a production level requirements.txt and keep that up to date for us. I suppose that's not very practical though as there's so many things you can add onto it, as it's a django app at heart.

Thanks again