Re: broken image on my django production site. Why is it?

2014-11-02 Thread Collin Anderson
Hello, You may need to install something like dj-static to serve your files. Collin -- 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...@go

Re: broken image on my django production site. Why is it?

2014-11-02 Thread Kakar Nyori
.path.join(BASE_DIR, > 'static'),# ) > > Finally, I ran server and I got still broken image shown on my page. When > I look the image carefully through "google inspect element",I can still see > the probably right path as below. > > > > But when I see

broken image on my django production site. Why is it?

2014-11-01 Thread rdyact
r and I got still broken image shown on my page. When I look the image carefully through "google inspect element",I can still see the probably right path as below. But when I see my /static/media/products/images/ folder, there were images created on development statge only, not the

Re: readonly unittests for production site

2010-04-15 Thread Thomas Guettler
Benjamin Reitzammer wrote: > Hi Thomas, > how did you make sure, that the tests are read-only? Did you apply any > special measures/tricks (like using a special DJANGO_SETTINGS_MODULE, > that has read-ony access to the database), or are your tests read-only > by convention and you trust the develop

Re: readonly unittests for production site

2010-04-15 Thread Benjamin Reitzammer
Hi Thomas, how did you make sure, that the tests are read-only? Did you apply any special measures/tricks (like using a special DJANGO_SETTINGS_MODULE, that has read-ony access to the database), or are your tests read-only by convention and you trust the developer that he/she does the RightThing?

readonly unittests for production site

2010-04-15 Thread Thomas Guettler
Hi, I use django since several months and wrote a lot of readonly unittests that I run on live systems. I think Django has only a infrastructure for test which use a temporary database. I am happy with my solution, but it would be nice to have the "infrastructure" in django itself. - A page to

Production site.

2010-02-08 Thread Massimiliano Bertinetti
with absolute path. Now all work, but I want to learn how to use continuos integration and having different machine to host my DBs (MySQL or PostgresSQL), Mercurial repositories and CI server and staging and production site in a consistent way, when my work grow.so, what can I post to you for l

Re: best practices for a production site

2008-01-21 Thread D. Hayes
Be sure and check out SVNMerge: http://www.orcaware.com/svn/wiki/Svnmerge.py It's a little Python script that helps ease the pain of merging. It's superfantastic. ( = On Jan 20, 7:59 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > On 20-Jan-08, at 2:06 PM, Andrew wrote: > > > This also may be

Re: best practices for a production site

2008-01-20 Thread Kenneth Gonsalves
On 20-Jan-08, at 2:06 PM, Andrew wrote: > This also may be a good time to consider a distributed version control > system (Like bazaar or mercurial)... we're just about to finish > porting to bazaar after running up to several situations just like > yours. > > One benefit of DVCS is that branchi

Re: best practices for a production site

2008-01-20 Thread Tim Chase
> This also may be a good time to consider a distributed version control > system (Like bazaar or mercurial)... we're just about to finish > porting to bazaar after running up to several situations just like > yours. I second this suggestion. Mercurial is currently at the top of my pick-list for

Re: best practices for a production site

2008-01-20 Thread Andrew
This also may be a good time to consider a distributed version control system (Like bazaar or mercurial)... we're just about to finish porting to bazaar after running up to several situations just like yours. One benefit of DVCS is that branching is easier than SVN...making feature-level branches

Re: best practices for a production site

2008-01-19 Thread Ned Batchelder
Updating to just a particular revision may work, but it is very easy for the trunk to get into a state where it would be hard to pick out just the fixes by updating specific files to specific revisions. This is labor intensive and confusing, and therefore error prone. Other people in this thre

Re: best practices for a production site

2008-01-18 Thread Kenneth Gonsalves
On 18-Jan-08, at 9:54 PM, William Siegrist wrote: > If the spelling changes are in 1 file, and the new feature is in > another file, can't you "svn update" just the spelling change file > and not the new feature file? And if they are in the same file, I > think the --revision option to svn

Re: best practices for a production site

2008-01-18 Thread Rajesh Dhawan
Hi Kenneth, > I have a site in production and being developed at the same time - a > common django usecase I am sure. This is the first time I am > developing a site with a team comprised of several remote > contributors also. My previous teams were all in the same lab. > Currently everyone with

Re: best practices for a production site

2008-01-18 Thread William Siegrist
If the spelling changes are in 1 file, and the new feature is in another file, can't you "svn update" just the spelling change file and not the new feature file? And if they are in the same file, I think the --revision option to svn update might also help. -Bill On Jan 17, 2008, at 11:55

Re: best practices for a production site

2008-01-18 Thread Marcin Mierzejewski
Hi Kenneth, I have very similar situation in my projects (some our projects, we develop 4 version in the same time - client specific versions). We do it in this way (we are using SVN): /trunk/ <- latest version /branches/product-1.0 /branches/product-1.1 /branches/product-1.2 /tags/product-1.0.0

best practices for a production site

2008-01-17 Thread Kenneth Gonsalves
hi, I have a site in production and being developed at the same time - a common django usecase I am sure. This is the first time I am developing a site with a team comprised of several remote contributors also. My previous teams were all in the same lab. Currently everyone with commit rig

Re: Debugging production site.

2007-08-14 Thread Merric Mercer
Just what I was looking for - many thanks MerMer Matt McClanahan wrote: > On Aug 13, 2:11 pm, Merric Mercer <[EMAIL PROTECTED]> wrote: > > >> Is there anyway to trap the debug information - so it is logged - but >> not visible to users? >> > > A good starting point is to use the ADMINS s

Re: Debugging production site.

2007-08-14 Thread Deryck Hodge
On 8/13/07, TheMaTrIx <[EMAIL PROTECTED]> wrote: > > Any idea why ADMINS would fail to send out the debug or 404 PNF mails > while your apps are sending email perfectly with the settings you put > in your settings.py for SMTP auth? Did you set your SERVER_EMAIL setting in addition to the EMAIL_HO

Re: Debugging production site.

2007-08-13 Thread TheMaTrIx
Any idea why ADMINS would fail to send out the debug or 404 PNF mails while your apps are sending email perfectly with the settings you put in your settings.py for SMTP auth? On Aug 14, 12:03 am, Matt McClanahan <[EMAIL PROTECTED]> wrote: > On Aug 13, 2:11 pm, Merric Mercer <[EMAIL PROTECTED]> wr

Re: Debugging production site.

2007-08-13 Thread Matt McClanahan
On Aug 13, 2:11 pm, Merric Mercer <[EMAIL PROTECTED]> wrote: > Is there anyway to trap the debug information - so it is logged - but > not visible to users? A good starting point is to use the ADMINS setting, which will give you a way to receive error reports via e-mail when debugging is off: h

Debugging production site.

2007-08-13 Thread Merric Mercer
I'm very occasionally getting errors reported to me on our production site by our members. However, we cannot replicate the problem ourself and because debugging is turned off the members are not giving me any real clues. Is there anyway to trap the debug information - so it is l

Re: Error In the production site

2007-05-04 Thread James Bennett
On 5/4/07, Grupo Django <[EMAIL PROTECTED]> wrote: > Hello, I get very often an error from modpython, and I have no idea > about what I should check, does anybody know it? You're seeing this particular traceback because an internal error occurred and you don't have a template for displaying the "

Re: Error In the production site

2007-05-04 Thread Grupo Django
I think it is because there is an error in the view, it happens suddenly. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To u

Error In the production site

2007-05-04 Thread Grupo Django
Hello, I get very often an error from modpython, and I have no idea about what I should check, does anybody know it? Here is the output: Mod_python error: "PythonHandler django.core.handlers.modpython" Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/mod_python/apache

Production site management

2007-03-04 Thread chasfs
I'm looking for some scripts to help manage Django based applications on a production site. Stuff like: -backing up and restoring the DB, code, media, html, etc. -promoting a test site to production -demoting a production site to the previous version Any recommendations? T

Best way to run dev and production site concurrently on same server? (take 2)

2006-09-21 Thread argus
Found this thread on the same topic http://groups.google.com/group/django-users/browse_frm/thread/7a2d69fa8748ba68 ..but it got closed. I want to do the same things as the OP in that thread: > I've recently completed a first milestone of a project and want to > publish it. I've got two URLs: www

Re: Best way to run dev and production site concurrently on same server?

2006-05-20 Thread Ian Holsman
tly I only have the dev website -- the current production > website > is static HTML. > > I was thinking the dev site could have it's own path separate from the > production website. The dev website is checked out from subversion as > the trunk and the production is checked o

Re: Best way to run dev and production site concurrently on same server?

2006-05-20 Thread Ian Holsman
, and allow you to share common things like user-id's across both. regards Ian On 21/05/2006, at 2:30 AM, Luke Plant wrote: > > On Thursday 18 May 2006 23:20, Rob Hudson wrote: > >> Based on my virtual hosts, can I have the production site list: >> SetEnv DJANGO_SETTIN

Re: Best way to run dev and production site concurrently on same server?

2006-05-20 Thread Luke Plant
On Thursday 18 May 2006 23:20, Rob Hudson wrote: > Based on my virtual hosts, can I have the production site list: > SetEnv DJANGO_SETTINGS_MODULE website.settings > and the dev site list: > SetEnv DJANGO_SETTINGS_MODULE website_dev.settings > and everything work? > > Is t

Best way to run dev and production site concurrently on same server?

2006-05-18 Thread Rob Hudson
out from tags. Based on my virtual hosts, can I have the production site list: SetEnv DJANGO_SETTINGS_MODULE website.settings and the dev site list: SetEnv DJANGO_SETTINGS_MODULE website_dev.settings and everything work? Is there something more I need to consider? Is anyone else do