[Catalyst] Distributing and updating Cat apps

Bill Moseley moseley at hank.org
Fri Apr 9 13:11:37 GMT 2010

On Thu, Apr 1, 2010 at 12:51 AM, Toby Corkindale <
toby.corkindale at strategicdata.com.au> wrote:

> We package things up into Debian-style packages, and then upload those to=
> local repository of packages.
> Then servers can just be updated using the standard system tools (apt).

Hi Toby,

This is really the direction I'm heading now (although it's looking like
CentOS and RPMs).  Can you answer a few general questions?

Are you using Template Toolkit?  How (or really where) are the templates
managed?   Where do they get installed, how does the TT View know where to
find them, etc?  Do they end up in /usr/share/<app>/ for example?

I'm sure you never have to roll-back a release, but I also assume you are
prepared to roll-back if needed.  How does that process work?

What about your static content (css, js, images)?  Where do those get

Any special tricks when using an app in "development" vs. production?  (For
example, under "dev" I use source css, js, but otherwise the app uses
combined and compresses css and js.

> You have a choice of either packaging up every single Perl dependency into
> a Debian package too (which is a world of pain), or installing all your
> dependencies into a local directory that you ship with the application. I
> recommend the latter.. (you'll still need to include dependencies on thin=
> like the C libraries for your database client, etc though, in the debian
> control file.)

We are doing a mix.  But, for the most part we are creating single modules
(packages).  Mostly that was to encourage inclusions of unit tests and just
more fine-grained management.  But, it is more work, true.

-- =

Bill Moseley
moseley at hank.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20100409/8d309=

More information about the Catalyst mailing list