Copying a site or creating a "dev" site
It would be great if we could create a development version of a site or copy a site in its entirety in order to work on it without the public eye.
As little downtime as possible is optimal when updating a site, but, in Harmony, it's currently fairly difficult to avoid treading on the live site when the live site and the new theme/pages have slightly different data fields. With most other self-hosted (ewwww) CMS's, I would just copy the live database and put a separate installation in a separate vhost.
2 Posted by John Nunemaker on 23 Aug, 2010 02:57 PM
We have some ideas on how to allow this, but there is definitely nothing
easy. Allowing copying an entire site would be the quickest but could lead
to confusion as to which is the most current. It also leads to lots of extra
stuff sitting around. Thanks for letting us know this would be helpful.
On Sun, Aug 22, 2010 at 2:20 PM, Elliott Pogue <
***@tenderapp.com<tender%***@tenderapp.com>
> wrote:
3 Posted by Torey Heinz on 06 Oct, 2010 02:35 AM
I second this.
I just meet with a client who needs to have all changes approved before publishing because of legality reasons. We already have the site in Harmony, but we are getting ready to make a number of updates.
At this point we are planning to create a copy of the site, for demo purposes, and then switch to it after approval.
This also brings up the idea of versioning, and the ability to stage unpublished changes.
Torey
Support Staff 4 Posted by Steve Smith on 07 Oct, 2010 07:20 PM
Versioning is something we've been discussing, and how we want to implement it. To be honest, though, unfortunately it's not on our short-list of features we're building right now. I'd say the temp site would be the best, if you want to put it that way, solution for now. Sorry I don't have a better answer right now.