My apologies for the long, long delay in finally responding. Your advice worked like a charm!!
Thanks a lot to all who responded. Ralph > On Oct 13, 2015, at 7:00 PM, Aaron C. de Bruyn <[email protected]> wrote: > > Without knowing too much about your environment, I figured I'd tell > you how I do it on my Debian-derivative systems. > > * Install python-virtualenv and virtualenvwrapper - These tools help > you create isolated python environments under your home folder under > '.virtualenv'. > * Create a virtualenv for the project. If my project name is CarSite > I run 'mkvirtualenv carsite'. (After the virtualenv is created it > should leave you *inside* the virtual environment) > * Install the latest version of Django into your virtual env by > running 'pip install django' > * Create your project by going in to your code folder (this is > different than your virtualenv) "cd ~/code" and then creating the > project "django-admin startproject carsite" > * Go in to the carsite directory "cd ~/code/carsite" > * Create a requirements.txt file for other developers ('pip freeze > > requirements.txt') > * Turn it into a git repo "git init ." > * Commit your new project (or make changes, then commit) "git commit > -m 'My first commit'" > * Connect it to github by following their directions (something like > 'git remote add origin [email protected]:username/carsite.git' and then > 'git push -u origin master') > > Now other developers should be able to start working on the project by > doing the following: > * cd ~/code > * git clone [email protected]:username/carsite.git carsite > * cd ~/code/carsite > * mkvirtualenv -r requirements.txt > > -A > > > > On Tue, Oct 13, 2015 at 5:38 PM, <[email protected]> wrote: >> Just to update: we also tried simply copying the entire virtual environment >> across, correcting for any differences in path. Still go the same behavior. >> >> We'd really welcome some advice on this one as otherwise we won't be able to >> use Django - we need a way to collaborate on implementation. >> >> Thanks >> Ralph >> >> >> On Tuesday, October 13, 2015 at 2:57:50 PM UTC-7, [email protected] wrote: >>> >>> Hi folks >>> >>> I'm a Django newbie (have found it very helpful!), so please excuse the >>> naivete. I have a question regarding team work on a Django project via >>> GitHub. >>> >>> I followed your excellent tutorial and have a virtual Python v2.7 >>> environment with Django 1.8.5 installed in it (FWIW: I thought I installed >>> Django 1.11, but django-admin --version shows 1.8.5). I then created my app >>> using "django-admin startproject foo" and got the project subdirectory as >>> expected. A quick check of the server showed the "Welcome to Django" page. >>> >>> I then added a bunch of model definitions and customized the admin page. I >>> verified that everything was okay by looking at the admin web page on my >>> localhost - the customized page is there, and I was able to add some test >>> data for one of the models. At this point, others want to pitch in to help, >>> and so I bundled everything in my project subdirectory (including manage.py >>> and the initial sqlite3 db) into a git repo and pushed it up to GitHub. >>> >>> The other team members also setup a virtual environment with Django, using >>> the same versions, and activated it. They then cloned the GitHub repo and >>> got all the project files as expected, and the directory structure looks >>> exactly the same. >>> >>> However, when they runserver in the project, they only get the "Welcome to >>> Django" page. The project admin and login page doesn't show up. I've >>> verified that all the model and settings info is correct, but we haven't >>> been able to get the info to show on the web page. >>> >>> Any suggestions on what we are doing wrong? I'm assuming a team can share >>> a Django project, but suspect we aren't collecting all the relevant files or >>> not getting the other team's environment set correctly. >>> >>> Thanks >>> Ralph >>> >> -- >> 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 [email protected]. >> To post to this group, send email to [email protected]. >> 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/b13c6d50-2a22-40bf-a78d-752a7305914a%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/MlbkfJcJo08/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > 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/CAEE%2BrGriRkeB5hZCd713eGvn05BzFnKUG3ASYN8T8vhS0rMdYg%40mail.gmail.com. > 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 [email protected]. To post to this group, send email to [email protected]. 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/AFCFFFEF-C79E-4D69-B13F-47FB05A59644%40open-mpi.org. For more options, visit https://groups.google.com/d/optout.
