Forums

Home / Developer Network / Forums / Sitefinity Older Versions (3.x): Deployment > Moving a site from dev to production

• Trevor

  Posted on Oct 20, 2010 (permalink)

  Hey guys,
  
  I'm doing an evaluation of Sitefinity for my company and one of their concerns is the ability to easily move a site from a dev environment to production, is this possible?
  
  Thanks,
  Trev

  Reply

• Answer Ivan Dimitrov Ivan Dimitrov

  Posted on Oct 20, 2010 (permalink)

  Hi Trevor,
  
  Procedure of moving Sitefinity to staging to production is the same as for each other ASP.NET website. Generally the steps are
  
  1. FTP all files from your solution to the production server
  2. Create a database backup on the staging server and restore it on the production.
  3. Change the web.config to point to the production database server.
  
  Another option is using database/schema comparison tool and file replication tools in case of merging frequently data between staging and production.
  
  Best wishes,
  Ivan Dimitrov
  the Telerik team

  Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

  Reply

• Trevor

  Posted on Oct 20, 2010 (permalink)

  Oh, perfect. Thank you.

  Reply

• Bryan

  Posted on Feb 18, 2011 (permalink)

  instead of changing the web.config as described in step three, wouldn't it make more sense to just not overwrite the production web.config in the first place?

  Reply

• Ivan Dimitrov Ivan Dimitrov

  Posted on Feb 21, 2011 (permalink)

  Hi Bryan,
  
  If there are changes in the web.config then you should merge them. For example - you have a new control that you want to add to the production.
  
  Best wishes,
  Ivan Dimitrov
  the Telerik team

  Vote for the 7 Telerik products at the 2011 Great Indian Developer Awards!

  Reply

• Bachar Zeidan

  Posted on Feb 24, 2011 (permalink)

  Hi,
  my site in actually under a pre-production server, with url named http:\\beta.mysite.com
  
  When I change the dns, the final name will be: http:\\mysite.com.
  
  I must do this in the weekend. :-|
  So, if I have some fixed links in html starting with http:\\beta.mysite.com\  it's a problem. What can I do to update my url into database? There's other thinks I have to update before the changing of url ?
  
  Best regards,
  Bachar

  Reply

• Ivan Dimitrov Ivan Dimitrov

  Posted on Feb 24, 2011 (permalink)

  Hello Bachar,
  
  We do not handle the static links and it depends on how you added them to a page.
  
  For public controls like GenericContent you have to update [sf_CmsControlProperty] table.
  For backend - modules you have to update -[sf_CmsTextContent]
  
  
  
  Greetings,
  Ivan Dimitrov
  the Telerik team

  Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!

  Reply

• thomas

  Posted on Mar 15, 2011 (permalink)

  What is considered a best practice for moving changes to an "already-in-production" site? To better explain, a Sitefinity project has already been pushed to production. However, there are modifications being made on a weekly basis. What is the best/easiest way to push these changes to the website?
  
  Thank you in advance

  Reply

• Ivan Dimitrov Ivan Dimitrov

  Posted on Mar 15, 2011 (permalink)

  Hi ,
  
  You can use a third party database replication and schema comparison tool to merge the changes without loosing data.
  
  Best wishes,
  Ivan Dimitrov
  the Telerik team

  Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!

  Reply

• thomas

  Posted on Mar 15, 2011 (permalink)

  Thank you for your response

  Reply

Home / Developer Network / Forums / Sitefinity Older Versions (3.x): Deployment > Moving a site from dev to production