Re: [Catalyst] go to chained action

Tomas Doran wrote: On 16 Dec 2009, at 13:18, Alex Povolotsky wrote: Hello! Having, for example, /controller/*/action handled by /controller/base (1) = /controller/action, how do I write correct go to /controller/argument/action ? just $c-go('/controller/argument/action') does not work.

Re: [Catalyst] go to chained action

Tomas Doran wrote: On 16 Dec 2009, at 13:18, Alex Povolotsky wrote: Hello! Having, for example, /controller/*/action handled by /controller/base (1) = /controller/action, how do I write correct go to /controller/argument/action ? just $c-go('/controller/argument/action') does not work.

Re: [Catalyst] go to chained action

2009/12/17 Alex Povolotsky tark...@over.ru: Tomas Doran wrote: On 16 Dec 2009, at 13:18, Alex Povolotsky wrote: Hello! Having, for example, /controller/*/action handled by /controller/base (1) = /controller/action, how do I write correct go to /controller/argument/action ? just

[Catalyst] Multiple deployments sharing code, data, and configuration

In our application, we have two parts - an indexing system that builds a set of databases, and a front end based on Catalyst. The issue we are facing is that each generated deployment runs almost exactly the same code, apart from needing different database references, and maybe a little