1-800-ATN-VERB
Mon-Fri 9AM-9PM ESTForum
Here be questions and here be answers.
1-800-ATN-VERB
Mon-Fri 9AM-9PM ESTHere be questions and here be answers.
Was wondering what the recommended process was for doing continued/support/bug fix development on a Vae site once it's gone "live". In particular what's the procedure for doing in-development deployments on a preview domain prior to doing a live production push? I couldn't find anything in the docs or designer/site portals that made this clear.
Biggest concern being that w/o the ability to do local server cloning or having a staging area that could be pushed to from a development SVN branch, we'd be forced to do dev testing of updates/changes on a live site... shiver.
Unless, of course, I'm missing something... which could always be the case.
Thanks,
Etienne
Hey Etienne,
I apologize for the fact that our docs are somewhat sparse in this regard, but we do support a number of things that should help you out.
First, we provide hosted Subversion repositories, which you may have seen here:
http://vaeplatform.com/post/subversion-and-verb
http://docs.vaeplatform.com/backstage.site.ftp
Secondly, we provide a local development environment that will let you develop locally on your machine without pushing to the server:
http://docs.vaeplatform.com/vae_local
Thirdly, we provide a separate staging and production environment hosted on our server. More info can be found here:
http://vaeplatform.com/post/release-production-environments
With these things combined, you should never have to do dev/testing on the live site.
Does this help answer your question?
Kevin
Manager
Kevin,
Definitely what I was looking for... I'm already familiar with using your SVN push configuration, just couldn't make heads or tails of where the line is drawn between a live site and preview/staging.
Didn't even realize you could do a local dev environment, that's gold!
Thanks,
Etienne
It looks like you're new here. If you want to get involved, click one of these buttons!
