[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-general
Subject:    Re: Seeking advice for redesign staging environment
From:       "Ryan O'Toole" <rotoole () gmail ! com>
Date:       2009-07-20 0:29:52
Message-ID: 81ad6ba10907191729v125ed672v754063eaab487ddd () mail ! gmail ! com
[Download RAW message or body]


I've used a development output channel before. It's straightforward and easy
to apply or not apply to a given story without disrupting people's work.
Just copy the dev template over the regular template when your ready to go
live. Then delete the dev templates and channel.

I've also used a separate development box, usually for large overhauls and
transitioning from one version of bric to another along with a redesign etc.
Great for getting a clean start.

Once tried creating a dev site on the same bric instance that people were
actively working in, and it just ended up causing confusion and headaches,
because people were not used to dealing with multiple sites and I was
inexperienced with configuring it to do that. I recommend avoiding this,
unless everyone involved is already familiar with running bric in that
manner.

--
ryan



On Tue, Jul 14, 2009 at 4:30 PM, Adam Wilson <adam@rfxtechnologies.com>wrote:

> I have never actually done this, BTW, so please let me know if it doesn't
> work as expected.
>
> > -----Original Message-----
> > From: Schults, Chris [mailto:chris.schults@pccsea.com]
> > Sent: Tuesday, July 14, 2009 4:29 PM
> > To: users@lists.bricolage.cc
> > Subject: RE: Seeking advice for redesign staging environment
> >
> > > If you are just making changes to the templates, you can create a new
> > site
> > > with aliases to stories on the existing site.
> > > When you are ready to make the staging version the real version, you
> > can just
> > > update the templates on the *real* site in bricolage and republish
> > everything.
> >
> > Thanks Adam. Might be about time to learn about Bricolage aliases then
> > .. I have been ignoring them all this time.
> >
> > Chris
>
>


[prev in list] [next in list] [prev in thread] [next in thread]