+1-888-365-2779
Try Now
More in this section

Forums / Deployment / Beta & Production

Beta & Production

4 posts, 1 answered
  1. Will
    Will avatar
    26 posts
    Registered:
    19 Aug 2008
    10 Dec 2009
    Link to this post
    Hey guys,

    This came up earlier than I was expecting, but my client wants to have both an on-line beta and the production site.  The idea is to create new features and content on the beta site, and then push the code changes and content out to the production in a rollout.  The problem is that they also want to use the same database for both sites as the beta site should have everything that the production site has, but the production site should not have anything from the beta site until the code is pushed and published to the production site.  Something like the beta site would see staged content and the production site sees published content.

    I don't think that Sitefinity 3.7 SP2 supports this model, so I'm wondering if you have any ideas.  I'm pretty sure that our only option is to have separate databases and to back populate the production database to the beta database after each rollout.  We would then be developing on stale production data.  Rollouts would consist of a normal ASP.NET rollout followed by content changes through the admin module.

    Is that the best option?  Also, is there anything in 4.0 for this scenario?

    Thanks,
    Bill
  2. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    11 Dec 2009
    Link to this post
    Hi Bill,

    Thank you for getting back to us.

    If you have multiple sites running on one DB you have two options- those sites will either share the content and both see the same content or you can set them up so that they do not share content just the DB then sites will not see each other'c content. There is no option in the middle.

    As to your customer's requirement - you are on the correct path to setting this up. Content can be replicated on production with database merges. First you will do the regular ASP.NET push to push custom code from staging to production, then you will take the staging and production DBs and compare them and push changes from staging db to production one.

    In Sitefinity 4.0 we will be introducing a syncronization service that will eliminate the manual part of this. It will all be done through SF's interface.

    Kind regards,
    Radoslav Georgiev
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
    Answered
  3. Will
    Will avatar
    26 posts
    Registered:
    19 Aug 2008
    11 Dec 2009
    Link to this post
    Hey Radoslav,

    Sounds good.  I look forward to using the new features in 4.0.  Is there any timeline on when it is going to be released?

    Thanks,
    Bill
  4. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    14 Dec 2009
    Link to this post
    Hello Bill,

    We have planned a release of a public beta in January 2010 and then the official version should be released in the first quarter of 2010.

    Greetings,
    Radoslav Georgiev
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Register for webinar
4 posts, 1 answered