Deploying to systems we have no access to. IT deployment han

Posted by Community Admin on 05-Aug-2018 04:29

Deploying to systems we have no access to. IT deployment handoff

All Replies

Posted by Community Admin on 05-Sep-2014 00:00

We are working on a website for a business with strict security requirements. We will not be given any form of access to there staging or production server. This is their first Sitefinity website, so there is not current procedure in place. For our production process, we have our own staging and development servers. However when it comes time for deployment on the clients servers, we will need a way to handoff the project and allow for updates following that. 

The current approach we have is to give read-only access to the clients IT staff. From there they could pull the project into the provisioned web server. SQL migrations would be handled in a similar fashion.

Does anyone have advice on a better approach? Is there a way to export/import a website?

Sitefinity 7.1, IIS 7.5, SQL Server 2008, Windows Server 2008 r2

Posted by Community Admin on 09-Sep-2014 00:00

Hi Aaron,

The scenario you are describing is viable in the cases that your work is solely based on code. In this case handing the solution files and DB is acceptible.

In the case the work you did is related to the DB only - i.e. content editing/creating/deleting I can recommend you look into our SiteSync module where you can easily sync content items, without having to backup entire databases.

Regards,
Ivan D. Dimitrov
Telerik

 
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
 

This thread is closed