Hi everyone,
I'm having a problem with the "auto_now_add" option for DateField.
I was under the impression that when you set this option, a datestamp
is set automatically for you. But when I try inserting records into my
database without supplying a date for this field, I get a NULL value
error:
OK. So for posterity's sake, I wanted to note that I solved this
problem, and it was completely my own embarrassingly stupid oversight
(is there a Jargon acronym for telling yourself to read your own
source more closely?).
The problem was not the project layout or Django code, but the link in
Ok. So are the additional dotted paths being added by the shell in
order to search the child directories of my project? It occurred to me
after I posted that the second of the three paths ( '/home/user/web/
project/..', ) might map to my static/ or templates/ directories, for
instance.
The third
So I'm continuing to look for the source of bugs on this front, and
wanted to add a note on a strange PYTHONPATH issue that I've
encountered.
When I fire up ipython from my project directory (using ./manage.py
shell) , the PYTHONPATH includes the following paths for my project:
Hey everyone,
Yes, this is yet another plea for help on configuring the dev server
for static media.
[insert disclaimer here about reading (and re-reading) docs,
countless tutorials, etc.]
I believe I have everything set up correctly, yet I can't seem to get
Django to serve static media on my
Hi Russell,
Thanks for the response. I'll admit, since I posted, I waved my hand
at the problem and imported all of my data through postgres. But I
think my problem might be related to what you describe below:
> > "Installing json fixture 'data2' from absolute path."
>
> This gives the first
Hey everyone,
While trying to load a json fixture, the contents are spitting out to
my bash shell but nothing is loading into the postgres database
backend.
>From inside my project directory, I'm executing the documented
command:
./manage.py loaddata data2.json
In addition to the contents,
> j...@john-laptop:~/Django/mysite$ ls -l
Try using the full path to the file rather than the ~ shortcut:
/home/username/Django/mysite/mysite_data.db
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users"
Is it better to create repositories at a site-, project- or app-level?
In other words, if I implement the conventional[1] directory structure
below, is it better to place the entire site (example.com) under a
single git repository, or would it be wiser to create separate git
repos for each
Hey everyone,
I'm' working on a basic chained select menu that lets you drill down
from county to town to restaurant. The men is populated dynamically
using ajax calls from browser to Django on the server side.
It's working as intended, but I'm wondering if there is a "best
practice" or
For posterity, I should point out that Graham's suggestion did indeed
work and the final set of problems stemmed from my django app code. I
had copied over some old code from my development environment to the
production server, but the dev server was running an older version of
django so the code
> ADMIN_MEDIA_PREFIX = '/media/'
>
> I guess I'd always assumed that this prefix was added on top of
> MEDIA_URL, but apparently not. Thus if on different site, looks like
> you need to state host as well.
>
> Graham
>
> On Nov 20, 3:06 pm, "Serdar T." <[EMAI
<<<>>>
On Nov 19, 10:58 pm, "Serdar T." <[EMAIL PROTECTED]> wrote:
> On Nov 19, 10:32 pm, Graham Dumpleton <[EMAIL PROTECTED]>
> wrote:
>
> > On Nov 20, 2:10 pm, "Serdar T." <[EMAIL PROTECTED]> wrote:
>
> > > h
On Nov 19, 10:32 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Nov 20, 2:10 pm, "Serdar T." <[EMAIL PROTECTED]> wrote:
>
> > hmm...I modified the root as you suggested but still the same results:
> > I get the admin page minus any stylesheets, etc.
at static media URLs will all be prefixed with that, then
> wouldn't:
>
> root /home/user/public_html/mysite/public/media;
>
> need to be:
>
> root /home/user/public_html/mysite/public;
>
> This is because you have location '/' on nginx mapped to this
> directory.
&g
Hello folks,
Can anyone out there offer advice on glitches in my production
environment, as well as explain the relevant settings.py in plain
English for a newbie?
I've been pulling my hair out for weeks trying to get an nginx reverse
proxy to serve static media while apache mod_wsgi serves up
for the suggestions.
On Nov 12, 7:04 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Nov 13, 6:48 am, "Serdar T." <[EMAIL PROTECTED]> wrote:
>
>
>
> > Can someone offer advice on server deployment headaches involving
> > apache/mod_wsgi/nginx? I seem to be
Can someone offer advice on server deployment headaches involving
apache/mod_wsgi/nginx? I seem to be having two problems:
1) Apache/mod_wsgi correctly serves dynamic content from a test app
(located in a ~/public_html directory) when the url starts with
"www". But apache reverts to serving the
18 matches
Mail list logo
