Setup dev site process and migrating orders from dev to live

[lancermedia]

We have a client that we are looking to move their current MMUI Miva store to Miva hosting. As I understand it, the basic process is:

1) Move live site to Miva (Miva will migrate site for free)
2) Miva sets up Dev subdomain as a copy of the live site (this is $40 we are told)
3) We can then run the MMUI to CSSUI conversion tool on the dev site
4) We can then apply a Ready Theme and customize

Now, when we are done with developing, we have 2 options to move the dev site to live

A) Miva will swap dev and live
B) Export framework and apply to live site

I've had mixed results in exporting a framework and successfully applying to another site. There's always something that seems to go wrong. So right now I'm leaning towards option A - however we would want to have the order/customers data synced between the 2 site before the swap is made.

We are being told by sales that this could be a 10 hour Professional Services job to sync orders. Is that correct? Seems like a LOT of time to just sync up orders and any new customers.

Curious on peoples thoughts.

Thanks!

-Kevin

[Rick Wilson]

That's all correct, one small change:

2) Miva sets up Dev subdomain as a copy of the live site (this is $40 we are told)

This is now free, we used to charge for these because they took a long time by a person but it's now automated. So you just submit a request via Support and we'll handle it without charge.

[lancermedia]

That's all correct, one small change:



This is now free, we used to charge for these because they took a long time by a person but it's now automated. So you just submit a request via Support and we'll handle it without charge.

Rick,

Thanks for the info. So I'm guessing there is a lot involved in syncing orders between dev and live before the swap? Thus the 10 hours of PS time? What is the rate for that?

-Kevin

[Rick Wilson]

I don't know the rate for that offhand (if we do it as a flat rate or not) but our normal rate is $125 an hour.

The issue is that depending on modules, etc... there can be a lot of manual data mapping and then QA to make sure it all goes right.

We've seen people before just shove new data in and then when internal database reference numbers eventually collide, you see really weird stuff, like new orders containing content of old orders, etc...

[Bruce - PhosphorMedia]

We recommend going the Save and Import as Framework method. While its true that there are sometimes little gotchas, the beauty of this method is that its repeatable. (Well, ok, the data migration is, if you know how to write Shell scripts.)

Create a Second dev site (let's call it test.domain.com) copy of the ORIGINAL site. And use that to test copying over the frame. Keep track of any 'whoops' you see, or correct their cause. Once you've killed the gremlims, you can do the Framework import on the original site with confidence.

[lancermedia]

We recommend going the Save and Import as Framework method. While its true that there are sometimes little gotchas, the beauty of this method is that its repeatable. (Well, ok, the data migration is, if you know how to write Shell scripts.)

Create a Second dev site (let's call it test.domain.com) copy of the ORIGINAL site. And use that to test copying over the frame. Keep track of any 'whoops' you see, or correct their cause. Once you've killed the gremlims, you can do the Framework import on the original site with confidence.

Bruce,

Thanks for the insight. Interesting on creating a 2nd dev site to test the rollout.


Rick,

Does Miva hosting allow for multiple dev sites? If so, what is the cost.

Also, is there a cost of maintaining a dev site and having it refreshed periodically? Say we keep a dev.domain.com and after 4 months want it refreshed to bring it up to date with the live site. Is that something Miva charges for? Come to think of it - I think I have a set of instructions lying around somewhere that I made about copying a live to dev subdomain.

-Kevin

[Rick Wilson]

Dev site creation is now automated, so there's no cost for setting one up regardless of the number of them.

Dev sites however are often abandoned and create some of the largest security issues on the web, so it's vital that you keep you Dev sites up to date on the latest version of Miva Merchant or you will be assessed Non Compliance and End of Life fees if you abandon one and leave it web accessible (as in on a web server connected to the internet, protecting it with a password doesn't suffice).

[lancermedia]

Dev site creation is now automated, so there's no cost for setting one up regardless of the number of them.

Dev sites however are often abandoned and create some of the largest security issues on the web, so it's vital that you keep you Dev sites up to date on the latest version of Miva Merchant or you will be assessed Non Compliance and End of Life fees if you abandon one and leave it web accessible (as in on a web server connected to the internet, protecting it with a password doesn't suffice).

Great! So no licensing issues with running 3 sites (live, dev, dev)? Other than some modules might complain.

-Kevin

[Rick Wilson]

Correct.

[lancermedia]

Correct.

Thanks Rick.

Is having 3 dev sites on the same Miva license exclusively a Miva hosting thing? I thought in the past Miva allowed 1 live and 1 dev site per license. If our client chooses not to move to Miva, is having 3 dev sites possible on 1 license?

-Kevin

[Rick Wilson]

No, if you're hosted externally only 1 Dev site per active license.

[lancermedia]

No, if you're hosted externally only 1 Dev site per active license.

Rick,

Thanks so much for the responses. We are suggesting to the client to have hosting move to Miva. Having multiple dev sites certainly is a nice feature (as well as free setup for those sites). I can see us only using that 3rd dev site as a test run for applying the framework like what Bruce mentioned. After everything is live we'd probably just kill it anyway.

So Miva will allow 3 sites on a license, where as on a 3rd party host, they would have to buy another Miva license to get that 3rd site - correct. Just want to be clear so the client has the right info to make the decision.

-Kevin

[Rick Wilson]

Our license management system limits external installs to 2 installs per root domain per license, so yes. I think people on third party hosts "get around" it by using our Free Developer Stores that we offer, but those have some other limitations.

[lesliekirk]

We recommend going the Save and Import as Framework method. While its true that there are sometimes little gotchas, the beauty of this method is that its repeatable. (Well, ok, the data migration is, if you know how to write Shell scripts.)

Create a Second dev site (let's call it test.domain.com) copy of the ORIGINAL site. And use that to test copying over the frame. Keep track of any 'whoops' you see, or correct their cause. Once you've killed the gremlims, you can do the Framework import on the original site with confidence.

I'd like to second the one dev, two dev process. No two MMUI to CSSUI conversion, create framework, then apply are the same. A checklist that I write up for one store may be entirely different that another. So having the "test dev" is a nice safety net, plus it helps you get a better understanding of how much time it's going to take for the final run.

The now free Miva hosted dev site configuration is a huge plus. Question for Rick - can a developer order it on behalf of the store owner or will the store owner still need to request it?

[lancermedia]

I'd like to second the one dev, two dev process. No two MMUI to CSSUI conversion, create framework, then apply are the same. A checklist that I write up for one store may be entirely different that another. So having the "test dev" is a nice safety net, plus it helps you get a better understanding of how much time it's going to take for the final run.

The now free Miva hosted dev site configuration is a huge plus. Question for Rick - can a developer order it on behalf of the store owner or will the store owner still need to request it?

Thanks Leslie.

So best case scenario that you like is:

1) Have live site
2) Copy live to dev1
3) Develop on dev1 (MMUI to CSSUI conversion + Ready Theme config/customization)
4) Save out dev1 framework
5) Copy live to dev2
6) Trial run of applying dev1 framework to dev2 - noting process and issues/fixes
7) Apply saved framework on live site redo all steps from #6
8) Drink ;-)

Obviously hosting with Miva allows the multiple dev sites which is good. Otherwise client would need to have another Miva license for 1 month to setup the dev2 site.

-Kevin