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

Forums / Developing with Sitefinity / Development Process w/Sitefinity

Development Process w/Sitefinity

4 posts, 1 answered
  1. Andrew Booth
    Andrew Booth avatar
    21 posts
    Registered:
    20 Jul 2009
    24 Feb 2010
    Link to this post
    I need some feedback on the process of how people are developing using sitefinity. We are trying to determine the best process to development using sitefinity. We have a development server, DMZ server, and our live production server. Initially we will create the content pages for clients and they will review and update them from the DMZ using the sitefinity cms.

    What we need to know, is what are other people doing as far as work flow. Especially when moving the site from the Development to DMZ and then to Production. Are you building the site and then just moving the files and then backing the database up and restoring the next server from the backup file?

    Any feedback or info on your process would be awesome so we can make an educated decision on how to control workflow would be great.

    Thanks!
    Andrew
  2. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    24 Feb 2010
    Link to this post
    Hi Andrew Booth,

    Thank you for using our services.

    What you are describing is a common setup of development, testing and production environments. This setup would normally save you some headache from the production environment going down due to new functionality included which might break the website. 

    You can also consider enabling Sitefinity's built in workflow for pages and generic content items if you customer needs a to control the creation, editing and publication of new pages and content items. The built workflow allows you to set up users belonging to different roles as approvers, publishers and content contributors. Thus you can even control workflow on production environment. 

    You can find more about the workflow feature in our User Manual.

    Greetings,
    Radoslav Georgiev
    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.
  3. Andrew Booth
    Andrew Booth avatar
    21 posts
    Registered:
    20 Jul 2009
    24 Feb 2010
    Link to this post
    Radoslav,

    Thanks for the reply. I do know about the workflow control, however, we are actually developing the websites before they are turned over to clients. We will be building, customizing and extending the modules and so on before we add content pages in. Once the site is built and the content pages are there we would move from the development server to the DMZ server for the client to update any outdated content as well as add new content before their site is rolled out live onto the production server.

    We are looking for a smooth effective way of moving the site from development all the way to production. (i.e. also moving the sitefinity database from one server).

    We are looking for the most efficient way to go about this. (rather than backing up the database and moving it via the backup file)
  4. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    24 Feb 2010
    Link to this post
    Hi Andrew Booth,

    Thank you for getting back to me.

    I now understand what you are looking fro exactly. Unfortunately Sitefinity does have website migration feature yet, we have something planned for our next major release. It will let you synch multiple Sitefinity deployments (content and page wise, also other information stored in db). For now the best recommendable approach would be using the backup restore, or detach/attach methods (more information here). 

    For assemblies, and other physical files you can use FTP from development to DMZ. You should however take into account differences in IIS setup in development and DMZ/production environent. For example you might be using different pipeline modes for example. Sitefinity websites work both in Classic and Integrated modes however if you make any configurations in web.config for example declaring Http handlers and modules you should do it in both sections (for classic and integrated mode) to make sure all works in all environments.

    I hope this post helps. I also wonder what our community members would have to share on this topic.

    Kind regards,
    Radoslav Georgiev
    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.
    Answered
Register for webinar
4 posts, 1 answered