Rebasing an application
Hi, I'm working on a module for rebasing Dancer applications. In short, it manipulates various $env components to make the request appear as coming to a different host and path, in order to address various problems that I encounter when I deploy the application behind a reverse proxy. It is implemented as a Plack middleware (inspired by Plack::Middleware::ReverseProxy but with a different approach) and I'd like some feedback about the module name. My idea is to call it Dancer::Middleware::Rebase, following the suggestions in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html Thoughts? Cheers, Flavio.
Franck worked on an issue of mounting several Dancer apps under different paths. Apparently, it's possible to do so with PSGI. Perhaps that will meet your needs. Franck, do you remember what I'm talking about? On Wed, Feb 9, 2011 at 3:54 AM, Flavio Poletti <polettix@gmail.com> wrote:
Hi,
I'm working on a module for rebasing Dancer applications. In short, it manipulates various $env components to make the request appear as coming to a different host and path, in order to address various problems that I encounter when I deploy the application behind a reverse proxy.
It is implemented as a Plack middleware (inspired by Plack::Middleware::ReverseProxy but with a different approach) and I'd like some feedback about the module name. My idea is to call it Dancer::Middleware::Rebase, following the suggestions in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html
Thoughts?
Cheers,
Flavio.
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
Hi, the module to solve my reverse proxy issues is ready and I like the idea of addressing them in one single point. Do you think that naming it Dancer::Middleware::Rebase is a problem? I wouldn't want to invade the namespace if this is considered "precious". Cheers, Flavio. On Wed, Feb 9, 2011 at 9:15 AM, sawyer x <xsawyerx@gmail.com> wrote:
Franck worked on an issue of mounting several Dancer apps under different paths. Apparently, it's possible to do so with PSGI. Perhaps that will meet your needs.
Franck, do you remember what I'm talking about?
On Wed, Feb 9, 2011 at 3:54 AM, Flavio Poletti <polettix@gmail.com> wrote:
Hi,
I'm working on a module for rebasing Dancer applications. In short, it manipulates various $env components to make the request appear as coming to a different host and path, in order to address various problems that I encounter when I deploy the application behind a reverse proxy.
It is implemented as a Plack middleware (inspired by Plack::Middleware::ReverseProxy but with a different approach) and I'd like some feedback about the module name. My idea is to call it Dancer::Middleware::Rebase, following the suggestions in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html
Thoughts?
Cheers,
Flavio.
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
Hmm... why Middleware, if I may ask? On Wed, Feb 9, 2011 at 1:37 PM, Flavio Poletti <polettix@gmail.com> wrote:
Hi,
the module to solve my reverse proxy issues is ready and I like the idea of addressing them in one single point.
Do you think that naming it Dancer::Middleware::Rebase is a problem? I wouldn't want to invade the namespace if this is considered "precious".
Cheers,
Flavio.
On Wed, Feb 9, 2011 at 9:15 AM, sawyer x <xsawyerx@gmail.com> wrote:
Franck worked on an issue of mounting several Dancer apps under different paths. Apparently, it's possible to do so with PSGI. Perhaps that will meet your needs.
Franck, do you remember what I'm talking about?
On Wed, Feb 9, 2011 at 3:54 AM, Flavio Poletti <polettix@gmail.com>wrote:
Hi,
I'm working on a module for rebasing Dancer applications. In short, it manipulates various $env components to make the request appear as coming to a different host and path, in order to address various problems that I encounter when I deploy the application behind a reverse proxy.
It is implemented as a Plack middleware (inspired by Plack::Middleware::ReverseProxy but with a different approach) and I'd like some feedback about the module name. My idea is to call it Dancer::Middleware::Rebase, following the suggestions in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html
Thoughts?
Cheers,
Flavio.
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
You MUST ask! :-) It's implemented as a Plack middleware, I'm just following the suggestion in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html- section "Namespaces". Of course I put "Dancer" instead of "MyFramework" :-) Cheers, Flavio. On Wed, Feb 9, 2011 at 12:56 PM, sawyer x <xsawyerx@gmail.com> wrote:
Hmm... why Middleware, if I may ask?
On Wed, Feb 9, 2011 at 1:37 PM, Flavio Poletti <polettix@gmail.com> wrote:
Hi,
the module to solve my reverse proxy issues is ready and I like the idea of addressing them in one single point.
Do you think that naming it Dancer::Middleware::Rebase is a problem? I wouldn't want to invade the namespace if this is considered "precious".
Cheers,
Flavio.
On Wed, Feb 9, 2011 at 9:15 AM, sawyer x <xsawyerx@gmail.com> wrote:
Franck worked on an issue of mounting several Dancer apps under different paths. Apparently, it's possible to do so with PSGI. Perhaps that will meet your needs.
Franck, do you remember what I'm talking about?
On Wed, Feb 9, 2011 at 3:54 AM, Flavio Poletti <polettix@gmail.com>wrote:
Hi,
I'm working on a module for rebasing Dancer applications. In short, it manipulates various $env components to make the request appear as coming to a different host and path, in order to address various problems that I encounter when I deploy the application behind a reverse proxy.
It is implemented as a Plack middleware (inspired by Plack::Middleware::ReverseProxy but with a different approach) and I'd like some feedback about the module name. My idea is to call it Dancer::Middleware::Rebase, following the suggestions in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html
Thoughts?
Cheers,
Flavio.
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
Ah, my bad. You already gave the link with an explanation and I overlooked it. Sorry. :) I think if the PSGI/Plack people have standardized Framework::Middleware, I have no objections at all. Hopefully we'll get to the "recommended plugins" in the website, so we could advertise it. I think it would be very useful for people, and might even close a ticket in the queue list for someone. Good job! :) On Wed, Feb 9, 2011 at 2:36 PM, Flavio Poletti <polettix@gmail.com> wrote:
You MUST ask! :-)
It's implemented as a Plack middleware, I'm just following the suggestion in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html- section "Namespaces". Of course I put "Dancer" instead of "MyFramework" :-)
Cheers,
Flavio.
On Wed, Feb 9, 2011 at 12:56 PM, sawyer x <xsawyerx@gmail.com> wrote:
Hmm... why Middleware, if I may ask?
On Wed, Feb 9, 2011 at 1:37 PM, Flavio Poletti <polettix@gmail.com>wrote:
Hi,
the module to solve my reverse proxy issues is ready and I like the idea of addressing them in one single point.
Do you think that naming it Dancer::Middleware::Rebase is a problem? I wouldn't want to invade the namespace if this is considered "precious".
Cheers,
Flavio.
On Wed, Feb 9, 2011 at 9:15 AM, sawyer x <xsawyerx@gmail.com> wrote:
Franck worked on an issue of mounting several Dancer apps under different paths. Apparently, it's possible to do so with PSGI. Perhaps that will meet your needs.
Franck, do you remember what I'm talking about?
On Wed, Feb 9, 2011 at 3:54 AM, Flavio Poletti <polettix@gmail.com>wrote:
Hi,
I'm working on a module for rebasing Dancer applications. In short, it manipulates various $env components to make the request appear as coming to a different host and path, in order to address various problems that I encounter when I deploy the application behind a reverse proxy.
It is implemented as a Plack middleware (inspired by Plack::Middleware::ReverseProxy but with a different approach) and I'd like some feedback about the module name. My idea is to call it Dancer::Middleware::Rebase, following the suggestions in http://advent.plackperl.org/2009/12/day-23-write-your-own-middleware.html
Thoughts?
Cheers,
Flavio.
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
participants (2)
-
Flavio Poletti -
sawyer x