Re: Running Django Project Locally

Maybe you can fix it by creating a new Django project in another directory and then copy manage.py (and/or other missing default files) to your current project directory.

On Wednesday, August 24, 2016 at 3:42:57 PM UTC+7, Lekan Wahab wrote:

Thanks for getting back to me.

​So, i just figured *manage.py* would also require the *settings.py* which is missing now.

What do i do about that?

Lekan​

On Wed, Aug 24, 2016 at 8:48 AM, Mike Dewhirst <mi...@dewhirst.com.au> wrote:

On 24/08/2016 5:23 PM, Lekan Wahab wrote:

Good morning,
I was recently given  a django project to manage at work.
However, i noticed the project has neither a django-admin.py or a manage.py file.
Is that normal?

There is usually a manage.py file in the root of the project. django-admin.py is put in the Python path when Django is installed.

If it is, how do i run the project on my local machine for testing purposes?

* Establish a virtualenv setup (optional but recommended)(separate topic)
* install the same version of Django locally (the file structure you show indicates a possibly older Django)
* install the same version of the database server locally
* dump the database on the server and load it locally
* mkdir ~/envs
* cd envs
|* ||python django-admin.py startproject projname (or use python3)

At this point you have the bones of the project into which you should be able to see where to copy the projname directories and files. After doing so ...

* ~/envs/projname$ python manage.py runserver

This will probably generate errors indicating which 3rd party packages need to be installed on the local machine. In theory when they are all installed you should be able to launch the software.
|
Good luck

Mike

The file structure is something like this:
Project Name
app1
app2
app3
app4
app5
models.py
forms.py
__init__.py
urls.py
views.py
admin.py


Each app contains the following:
models.py
forms.py
__init__.py
urls.py
views.py
admin.py
--
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...@googlegroups.com <mailto:django-users+unsubscribe@googlegroups.com>.
To post to this group, send email to django...@googlegroups.com <mailto:django...@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAE6v7ocLOQh_HMxiu29%2Br3wLANJ2wjtesyjb79SXmFXpgb8jgw%40mail.gmail.com <https://groups.google.com/d/msgid/django-users/CAE6v7ocLOQh_HMxiu29%2Br3wLANJ2wjtesyjb79SXmFXpgb8jgw%40mail.gmail.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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f61e75cb-12f3-3fe8-e792-a5ce69f473c3%40dewhirst.com.au.

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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/97598bc5-d0c5-4c83-bda0-d3c6b2824fc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.