Perfect - thanks all!
On Jan 30, 2:04 pm, "Noah Kantrowitz" <[email protected]> wrote:
> Or, better yet, use the --autoreload flag to tracd so it will automatically
> restart when it detects a code change. Combine this with setuptools'
> develop-mode installation and the auto_reload flag in trac.ini (which forces
> templates to reload on change too) and you can just edit your code directly
> and instantly see the changes reflected.
>
> --Noah
>
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]]
> > On Behalf Of Remy Blank
> > Sent: Friday, January 30, 2009 10:03 AM
> > To: [email protected]
> > Subject: [Trac] Re: Changes to my plugin aren't detected by Trac/Apache
> > unless Apache is restarted?
>
> > Stodge wrote:
> > > I'm learning how to write Trac plugins and I have a very simple one
> > > for when a ticket is changed. However, changes I make to this plugin
> > > only run when I do /etc/rc.d/init.d/httpd graceful. Is this really
> > > necessary or am I missing something simple as to why changes to my
> > > plugin aren't detected by Trac/Apache.
>
> > Yes, this is necessary, unless you use CGI (which is not recommended).
>
> > However, for development, you should use tracd in foreground mode on a
> > test Trac instance, so that you can easily restart it.
>
> > -- Remy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
