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

Forums / Deployment / Best Practice for Deployment?

Best Practice for Deployment?

6 posts, 0 answered
  1. Tony
    Tony avatar
    23 posts
    Registered:
    12 Sep 2008
    06 Oct 2008
    Link to this post
    Maybe this was touched on in the past, but what is the best practice when it comes to deploying a project?

    Develop locally, everything down to the last bit of content and then (somehow) copy everything out?

    or maybe get all your UI stuff ready, any custom code and then install from scratch on the server, copying all customizations out to the production server and then loading the content?

    Having never deployed with this CMS before I would appreciate any input as well as any tips & tricks you guys know to make it go smoothly.

    In my case the Sitefinity site will be replacing the current production server, but it will be on completely seperate hardware and therefore can exist at the same time as their current site.
  2. Pepi
    Pepi avatar
    981 posts
    Registered:
    28 Oct 2016
    07 Oct 2008
    Link to this post
    Hi Tony,

    Please refer to the instructions in our User Manual > Working with Web Site Projects > Migrating Projects to the Production Web Server.

    Hope this helps.

    Best wishes,
    Pepi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. Tony
    Tony avatar
    23 posts
    Registered:
    12 Sep 2008
    07 Oct 2008
    Link to this post
    Yes, those are the instructions on how to migrate to production, but that doesn't really answer my question. 

    I guess what I want to know is, when you are working on a Sitefinity project what is your process?  Develop locally and then copy it out or develop the UI and then set everything up in Production.  And why do you do it that way? (benefits/drawbacks)
  4. Joe
    Joe avatar
    138 posts
    Registered:
    24 Sep 2012
    07 Oct 2008
    Link to this post
    Hello Tony,

    Thanks for the follow up.

    We would recommend developing the project locally and then adding content on the production server. You should do all of your custom module development, add meta fields to the modules (if necessary) and adjust master pages and themes on the development server. This way, you can ensure everything works before pushing it to the production server. Since Sitefinity uses workflow and a user can preview a page before it is published, you should add the content on the production server instead of the development server. This way, you don't have to migrate content from one database to another. There is one drawback to doing things this way; you would need to copy the files from the development server to the production server using an FTP like FileZilla for example. For more info on workflow, please read Page Workflow in our User Manual.

    I hope that I have clearly answered your question, Tony. Please contact us if you have any other questions.


    All the best,
    Joe
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  5. Elizabeth
    Elizabeth avatar
    83 posts
    Registered:
    23 Mar 2005
    17 Dec 2008
    Link to this post
    There is one drawback to doing things this way; you would need to copy the files from the development server to the production server using an FTP like FileZilla for example.

    Copy which files from dev to production using FTP?
  6. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    18 Dec 2008
    Link to this post
    Hello Elizabeth Munsey,

    In case you finished with the development, and want to move the project to live server, you should upload all files. In case you just modified some of the files, you should upload only those files.

    I hope this helps.

    Best wishes,
    Georgi
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Register for webinar
6 posts, 0 answered