Mailing List Archive: Catalyst: Users

FastCGI on dev. server, reloading modules?

Index | Next | Previous | View Threaded

c.kras at pcc-online

Sep 19, 2009, 4:54 AM

Post #1 of 5 (1170 views)
Permalink

FastCGI on dev. server, reloading modules?

Hi,

So far I've always tested my Catalyst apps running through CGI. Since FastCGI gives such a performance boost I was wondering if I can test with FastCGI without having to manually restart my instances after I've made a change to a controller/model/view/anything.

Is this possible or will it only give me headaches?

Thanks.

Christiaan

_______________________________________________
List: Catalyst [at] lists
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
Dev site: http://dev.catalyst.perl.org/

bobtfish at bobtfish

Sep 19, 2009, 6:02 AM

Post #2 of 5 (1078 views)
Permalink

Re: FastCGI on dev. server, reloading modules? [In reply to]

On 19 Sep 2009, at 12:54, Christiaan Kras wrote:
> So far I've always tested my Catalyst apps running through CGI.
> Since FastCGI gives such a performance boost I was wondering if I
> can test with FastCGI without having to manually restart my
> instances after I've made a change to a controller/model/view/anything

Why would you want to do that?

Why aren't you using the development server for development?

Cheers
t0m

_______________________________________________
List: Catalyst [at] lists
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
Dev site: http://dev.catalyst.perl.org/

c.kras at pcc-online

Sep 19, 2009, 6:23 AM

Post #3 of 5 (1071 views)
Permalink

RE: FastCGI on dev. server, reloading modules? [In reply to]

Because the less difference between the development and production server the better. It lessens the amount of possible problems that can arise when deploying the application to the production server.

Christiaan

-origineel bericht-
Onderwerp: Re: [Catalyst] FastCGI on dev. server, reloading modules?
Van: Tomas Doran <bobtfish [at] bobtfish>
Datum: 19-09-2009 15:02

On 19 Sep 2009, at 12:54, Christiaan Kras wrote:
> So far I've always tested my Catalyst apps running through CGI.
> Since FastCGI gives such a performance boost I was wondering if I
> can test with FastCGI without having to manually restart my
> instances after I've made a change to a controller/model/view/anything

Why would you want to do that?

Why aren't you using the development server for development?

Cheers
t0m

_______________________________________________
List: Catalyst [at] lists
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
Dev site: http://dev.catalyst.perl.org/

_______________________________________________
List: Catalyst [at] lists
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
Dev site: http://dev.catalyst.perl.org/

melo at simplicidade

Sep 19, 2009, 8:00 AM

Post #4 of 5 (1075 views)
Permalink

Re: FastCGI on dev. server, reloading modules? [In reply to]

Hi,

On 2009/09/19, at 14:23, Christiaan Kras wrote:

> Because the less difference between the development and production
> server the better. It lessens the amount of possible problems that
> can arise when deploying the application to the production server.

I use the same setup: local nginx, all my development is done with Cat
under fastcgi. But no, I could not find any workaround for restarting
the service.

melo

>
> Christiaan
>
> -origineel bericht-
> Onderwerp: Re: [Catalyst] FastCGI on dev. server, reloading modules?
> Van: Tomas Doran <bobtfish [at] bobtfish>
> Datum: 19-09-2009 15:02
>
>
> On 19 Sep 2009, at 12:54, Christiaan Kras wrote:
>> So far I've always tested my Catalyst apps running through CGI.
>> Since FastCGI gives such a performance boost I was wondering if I
>> can test with FastCGI without having to manually restart my
>> instances after I've made a change to a controller/model/view/
>> anything
>
> Why would you want to do that?
>
> Why aren't you using the development server for development?
>
> Cheers
> t0m
>
> _______________________________________________
> List: Catalyst [at] lists
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
> Dev site: http://dev.catalyst.perl.org/
>
>
> _______________________________________________
> List: Catalyst [at] lists
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
> Dev site: http://dev.catalyst.perl.org/

_______________________________________________
List: Catalyst [at] lists
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst [at] lists/
Dev site: http://dev.catalyst.perl.org/

jshirley at gmail

Sep 19, 2009, 8:40 AM

Post #5 of 5 (1071 views)
Permalink

Re: FastCGI on dev. server, reloading modules? [In reply to]

On Sat, Sep 19, 2009 at 6:23 AM, Christiaan Kras <c.kras [at] pcc-online>wrote:

> Because the less difference between the development and production server
> the better. It lessens the amount of possible problems that can arise when
> deploying the application to the production server.
>
> Christiaan
>
>
The development server is more similar to FastCGI (or Prefork) than running
under plain CGI. Unless, of course, you are deploying under CGI and if that
is the case you have many other problems.

-J

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads