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

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

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?


In reply to Re: Catalyst deployment headscratchings by jplindstrom
in thread Catalyst deployment headscratchings by stonecolddevin

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (4)
As of 2023-03-30 05:57 GMT
Find Nodes?
    Voting Booth?
    Which type of climate do you prefer to live in?

    Results (73 votes). Check out past polls.