Django on shared hosting - no effect until restart

I'm trying to setup shared Django hosting on FreeBSD with
Apache, but
I have to restart Apache every time when I want changes to
take
effect, insead of  simply touching file.
Calling FastCGI file directly have same results- no effect
until restart.
Is this FastCGI problem or I have to look somewhere else?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On 8/30/06, viestards <viestards.listsgmail.com> wrote:
>
> I'm trying to setup shared Django hosting on FreeBSD
with Apache, but
> I have to restart Apache every time when I want changes
to take
> effect, insead of  simply touching file.
> Calling FastCGI file directly have same results- no
effect until restart.
> Is this FastCGI problem or I have to look somewhere
else?
>

With FCGI, do a touch on your .fcgi file. That always works
for me.

Easier way of course is to develop with the built-in
development
server, and only start Apache when your development is done.

Jay P.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

> With FCGI, do a touch on your .fcgi file. That always
works for me.

I write "aaa" in fcgi file, which must cause
syntax error, save it,
but nothing happens.

> Easier way of course is to develop with the built-in
development
> server, and only start Apache when your development is
done.

My hosting provider will not restart server every time when
I need it.
Maybe it's fcgi fault, now default FreeBSD FastCGI package
is used,
and it's built as DSO. Maybe I have to build it other way.

> Jay P.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On 8/31/06, viestards <viestards.listsgmail.com> wrote:
> My hosting provider will not restart server every time
when I need it.
> Maybe it's fcgi fault, now default FreeBSD FastCGI
package is used,
> and it's built as DSO. Maybe I have to build it other
way.

Apache itself shouldn't require a restart, just the Django
FastCGI
processes. I run FastCGI behind lighttpd, and change stuff
all the
time; I just stop and start my FastCGI processes and leave
lighttpd
alone.

-- 
"May the forces of evil become confused on the way to
your house."
  -- George Carlin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On 8/31/06, James Bennett <ubernostrumgmail.com> wrote:
> Apache itself shouldn't require a restart, just the
Django FastCGI
> processes. I run FastCGI behind lighttpd, and change
stuff all the
> time; I just stop and start my FastCGI processes and
leave lighttpd
> alone.

I haven't done anything with FastCGI, and only a little
with lighty,
but you can usually force a config reload by sending HUP to
the
interesting process:

kill -s HUP <your pid here>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---