how to set up a "preview" of MWF 1.3 for content providers?

[BerkeleyEdu]

Hi,

I'd like to provide a "preview" instance of MWF 1.3 to make for a smooth transition. I think you did this at UCLA. How do I go about having both 1.2 and 1.3 running on the same server?

I could ask them to use m-qa.berkeley.edu until everyone was converted but seems wrong to use QA for production.

-Sara

[ebollens]

Sara, we put it under m.ucla.edu/preview13 and set up an Apache alias to that path. In doing so, even when we changed the Apache docroot to refer to the 1.3 instance of our deployment, we just left the alias in, so if people didn't switch over, we wouldn't hurt them.

That said, if I were in your shoes, I wouldn't be opposed to using the m-qa server before you deploy it officially. That was the purpose of the preview13 deployment, which occurred (two weeks) before we officially upgraded so as to give people time to test.

After we updated m.ucla.edu itself, we then put up an Apache alias m.ucla.edu/12 that refers to the old MWF 1.2 installation - just in case people couldn't get their apps updated before the deadline.

[BerkeleyEdu]

|S||o...you put 1.3 somewhere like "/var/www/html/mwf13/" and used an
Apache alias | "|m.ucla.edu/preview13"||to point to it for preview.

Then you |pointed m.ucla.edu at the same directory for the official
release.

And for late adopters, pointed |m.ucla.edu/12 to the old
"/var/www/html/mwf" directory.|

I guess there is nothing magic about the current version of MWF residing
in a directory called "mwf"?

The QA could work as a preview for testing purposes, but occurs to me
that people might need to make changes that are not compatible with 1.2
so would need a production version of 1.3 to switch to at their own pace.

-Sara

On 9/1/12 2:19 PM, Eric Bollens wrote:

Sara, we put it under |m.ucla.edu/preview13| and set up an Apache
alias to that path. In doing so, even when we changed the Apache
docroot to refer to the 1.3 instance of our deployment, we just left
the alias in, so if people didn't switch over, we wouldn't hurt them.

That said, if I were in your shoes, I wouldn't be opposed to using the
m-qa server /before you deploy it officially/. That was the purpose of
the |preview13| deployment, which occurred (two weeks) before we
officially upgraded so as to give people time to test.

After we updated |m.ucla.edu| itself, we then put up an Apache alias
|m.ucla.edu/12| that refers to the old MWF 1.2 installation - just in
case people couldn't get their apps updated before the deadline.

—
Reply to this email directly or view it on GitHub
#163 (comment).