Good points. I tend to merge the roles of developer and QA in my mind when
thinking of Django, since it is not my day-job and I'm working alone. That
said, you are correct, when doing something more than quick-hit problem
resolution, I'm guessing I'd wind up going back to runserver. I do stil
One thing I'd add to this is that I could never work without runserver
because I tend to use ipdb a *lot* while debugging any problems. For me the
best way to debug is to put import ipdb; ipdb.set_trace() in my code and
just start debugging from the command line. Having uwsgi or any other kind
of s
2016-08-24 17:54 GMT+02:00 Michael Macdonald :
> Interestingly enough, just this morning, after a couple times being bitten
> with differences in behavior between use of runserver in development vs.
> wsgi in production, I've decided to do all development on my local machine
> under lighttpd. In
Interestingly enough, just this morning, after a couple times being bitten
with differences in behavior between use of runserver in development vs.
wsgi in production, I've decided to do all development on my local machine
under lighttpd. In the process of (mis?)configuring it now.
I'm prett
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 figure
So,
I have been handed the other part of the project which now contains
everything except the manage.py file(which i have created).
Also, the project is quiet old and some of the dependencies are either no
longer being managed or don't exist anymore.(unobase for an example).
As such, i was handed
On 24/08/2016 6:42 PM, 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?
That depends. Is the system currently working?
If so there will be a bunch of settings somewhere and
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
wrote:
> On 24/08/2016 5:23 PM, Lekan Wahab wrote:
>
>> Good morning,
>> I was recently given
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
Hi,
It's definitely weird to not have a manage.py since all new Django
projects should have it by default. But the manage.py file is pretty
simple, and you can just paste this inside a new manage.py:
#!/usr/bin/env python
import os
import sys
if __name__ == "__main__":
os.environ.setdefaul
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?
If it is, how do i run the project on my local machine for testing purposes?
The file structure is something like this:
Project
11 matches
Mail list logo
