Hi - I am kind of new myself, and I don't have all the answers to your
questions, but here are some thoughts, and I could be wrong.
1. You can set up your virtualenv anywhere you like. The one I'm using
right now is in ~/Envs/venv_for_my_project/ All you're doing with it is
source/bin/activate. As Two Scoops of Django recommends, just store the
output of pip freeze in version control.
2. I am not using Eclipse, so I can't help there. I am using PyCharm which
has a nice integration with virtualenv and Django. It's easy to start the
server in debugging mode and set break points. With Pycharm, I set it up
once, pointing it to the location of my virtualenv, and haven't touched it
since, even though I've added packages to my virtualenv. The downside of
PyCharm is that it costs money.
3. I don't think you can screw things up too much. You may want to first
do as much as possible via the command line in a terminal window and see if
that works (for example, start and stop the server), then try the same
thing through Eclipse's interface. The worst that can happen is that your
test server doesn't work.
On Sat, Jul 19, 2014 at 3:09 PM, Martin Torre Castro <mad...@gmail.com>
wrote:
> Hello,
>
> my name is Martin and I'm a computer engineer from Spain. I'm going to
> start a new project with a colleague and I decided to use Django because we
> searched for free opensource tools and I'm in love with Python.
>
> We have made a couple of tutorials (the official one and "Tango with
> django"). I've also bought the book "Two scoops of Django" for the 1.6
> Django edition. We're starting the project soon as well as we finish the
> design, but I'm concerned about setting up the new environment. We're
> thinking of using:
>
>
> - postgresql
> - Python/Django [ of course ;-) ]
> - Eclipse/Pydev
> - Git
> - jQuery
>
> I've been reading the Greenfield/Roy book and some web sites and I want to
> set up the environment with good practices by using virtualenvwrapper,
> virtualenv, pip, the requirements.txt files and so on.
> I have made some mix for all this, but I would be grateful if someone
> could confirm us if we are on the right way, give us some advice or maybe
> tell us where on the internet we can find a good way of doing all this.
>
> My preview for the whole setting up is next:
>
>
> 1. We should start the installations by installing "sudo apt-get
> install virtualenvwrapper" . If I understand correctly, this installs
> virtualenv as well as an embedded pip.
> 2. The virtualenv must be created ("virtualenv env") in the parent
> directory of the Eclipse workspace, I suppose. This is one point of
> confusion to me. I don't know either if I have to activate this every time
> I come back for developing resuming the work from days before. I completely
> understand that later from Eclipse I will give the python path inside the
> virtualenv, but don't know if must activate the virtualenv every time.
> 3. Next step would be to install all the things we need (django,
> pillow, psycopg2) using a requirements.txt file. "pip install -r
> requirements.txt"
> 4. We should create the new django project with a python
> django-admin.py startproject <project_name>
> 5. Now I don't know if we should link the project to an already
> installed version of Eclipse or run the "git init" first. I understand
> that Eclipse and Git don't need to be installed inside the virtualenv. In
> fact, I've been reading and it seems that Eclipse can work OK just by being
> given the path inside the virtualenv where the python executable is
> located. I've also read that some people used to make different workspaces,
> but configuring the paths should be enough
> http://stackoverflow.com/questions/1145374/virtualenv-with-eclipse-galileo
>
> From here I would just upload to github or bitbucket, maybe doing the
> whole thing from Eclipse would be easier. But the integration with Eclipse
> when we made tangowithdjango tutorial was the difficult point, because
> there is no option for importing a django project from Eclipse (Kepler
> version last time). We found easier to create the project from Eclipse, but
> we were not using a virtualenv for the tutorial.
>
> I haven't used virtualenv before, so it's our second main obstacle, but I
> expect it will be easy when we get used to it (^_^) .
>
> Please could someone help with some piece of advice, pros and cons of
> every option. Just don't want to do something now I will regret in future.
>
> Thank you veeery much in advance.
>
> PS: Some links visited:
> http://www.dabapps.com/blog/introduction-to-pip-and-virtualenv-python/
> http://www.tangowithdjango.com/book/chapters/setup.html
> https://virtualenv.pypa.io/en/latest/virtualenv.html
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/f7332cab-26a7-45fe-a9f5-26831da6bdf4%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/f7332cab-26a7-45fe-a9f5-26831da6bdf4%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAB0b4%2ByNtxNqOEbgi%3D_%3D5dNrjDR0zwp3pDFrfUyJLwksSEpy5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
