Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Catalyst deployment headscratchings

by stonecolddevin (Parson)
on Nov 06, 2008 at 11:08 UTC ( #721952=perlquestion: print w/replies, xml ) Need Help??

stonecolddevin has asked for the wisdom of the Perl Monks concerning the following question:

Dear Monks,

I have a question about deploying Catalyst apps.

I've tried various methods, but they've either been "unprofessional", or pretty much sloppy.

Currently, I do an svn export of my working copy, tar/gz that all up, SFTP to my server, uncompress, and fiddle to get things working (namely, chmod +x dispatch.fcgi, perl script/, etc.).

This still seems a bit clunky to me, and being fairly new to a polished deploy process, I was wondering if any experts had any advice, as this process lends itself to a few errors including a bit of a lengthy process to do the aforementioned steps, as well as some of the annoying fiddling/fenaggling to get things working properly.

Does anyone else have a more refined process?



Replies are listed 'Best First'.
Re: Catalyst deployment headscratchings
by almut (Canon) on Nov 06, 2008 at 12:17 UTC

    What you describe doesn't sound too unprofessional to me. The only thing that I'd consider "unprofessional" is doing all the steps by hand every time... After all, Perl is the perfect glue language for automating such tasks, in particular in real-world situations, where things are often somewhat ugly due to the various idiosyncrasies of the deployment environment (which are sometimes beyond your immediate control).

Re: Catalyst deployment headscratchings
by jplindstrom (Monsignor) on Nov 06, 2008 at 13:45 UTC

    That doesn't sound too terrible, except for the manual fiddling. That's terrible :)

    Start off with a manual process, but, three strikes and then you automate. Especially important and error prone and stressful things like making a release and deploying it to an environment (release and deployment are two different things). It should be as effortless as running a script with some config options.

    We use Templare Toolkit to generate config files (e.g. httpd.conf) from templates, with current release and deployment values.

    You should have a process in place (and by process I mean a checklist of what needs to be done, and scripts to automate anything automatable), maybe on a Wiki page. There are probably non technical steps here: telling people before and after the upgrade, assembling a set of release notes, updating the list of what's deployed where (unless you automated that too).

    The only thing in your description that sounds odd is exporting the working copy. Wouldn't it be better to base the release of a clean check out to a temp directory, so you're 100% certain it contains what's in the repo and nothing else?


      Wouldn't it be better to base the release of a clean check out to a temp directory, so you're 100% certain it contains what's in the repo and nothing else?
      I agree. Additionally, I would do a svn copy to tag the release.

      When using cvs it could look like this:

      REV=MyApp-0-2-1-b mkdir -p /tmp/$REV cd /tmp/$REV cvs export -r $REV MyApp tar -cvf $REV.tar MyApp bzip2 $REV.tar rm -rf MyApp
      I guess a similar thing is possible for subversion also.
      No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://721952]
Approved by almut
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (2)
As of 2023-09-24 09:52 GMT
Find Nodes?
    Voting Booth?

    No recent polls found