Change requirements.txt file according to a fresh install.

[iulianstana]

According to pip-installer user_guild I change the requirements.txt file. For each package there is a version. I just put all my installed packages from pip freeze to requirements.txt.

For the moment the server is running with this requirements. When the time will comes the version of some packages can be easy change.

pip guild: http://www.pip-installer.org/en/latest/user_guide.html

[brainstorm]

I am not sure about version pinning this so tightly. For instance, I managed to get Django 1.6 working without issues with the ansible deployment roles and no version pinning:

https://github.com/brainstorm/ansible-neurostars.org

For instance, have a look at those requirements.txt:

https://github.com/chapmanb/bcbio-nextgen/blob/master/requirements.txt

They pin to avoid legacy but are open to future upgrades. If things break when pulling new versions of the dependencies, neurostars should be fixed. Holding strictly into specific versions leads to technical debt in my experience.

[iulianstana]

Yeah, you are right. I am sure that the legacy must be avoid when you can and probably I made a quick commit.

The problem is that the requirements.txt file from neurostars.org branch it's a bit broken. I don't know about others, but I get some errors when I try simply to call 'pip install -r requirements.txt'. This was the first problem that I had encountered.

About django version, with a fresh installation I get errors for markup module. I saw that you already know about this issue, but I think that changing django version to >= 1.5 will give a better hint to new contributors. Just for the moment, until this issue will be fixed.

[brainstorm]

Humm, strange, can you please have a look at the automated ansible deployment here?:

https://github.com/brainstorm/ansible-neurostars.org

With those automated roles, I don't get any of the errors you describe.