How best to do a development site
How Do I?
I’m in the process of developing a new site for my organization. One thing that I’ve always had on the big, institution sites I’ve maintained is a development site where I could, for example, load up a new extension to see if it broke anything. As a rule, the dev site has always been restricted, not publicly accessible. I’m guessing this is pretty common.
The thing with ExpressionEngine, though, is that it doesn’t appear to like this model. I have another site that I’ve already launched. As I built it, I also set up a dev site for which I used the same license as the production site. Looking at my Manage Purchases section here on the EllisLab site, I get a “This license is in use on multiple domains” message.
I could purchase a new license for this, or use Multiple Site Manager, but both solutions seem excessive, at least at the moment.
What do you all think? Anyone have any suggestions?
Thanks.
L.
You’re all good, buddy. From the License Agreement:
An ExpressionEngine license purchase allows a single “live” installation in a production environment and ancillary “development use only” installations as needed to support the live installation (such as development and a staging servers).
https://ellislab.com/expressionengine/user-guide/about/license.html
I had the same issue because our development sites are all run off a single domain instead of on the actual domains where the production sites reside. I was getting the same message, and when I contacted support, they assured me this wasn’t a problem and that they would contact licensees (us) first if they felt there was a problem.
Thanks. Good to know.
L.