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

Forums / General Discussions / What files to sync in web farm?

What files to sync in web farm?

6 posts, 0 answered
  1. JeremyL
    JeremyL avatar
    3 posts
    Registered:
    27 Oct 2009
    28 Oct 2009
    Link to this post
    We run everything in a web farm / load balanced environment. I've been reading around and this is what I understand about Sitefinity and how it works in that enviroment.

    1. We need to set the cache to be stored in the DB
    2. Any and all images, attachements (like PDF's ect) added by our writers end up in the database
    3. There are other files like user controls that can be uploaded via the interface that are not added to the database so would need to be sync'ed some how.

    Do you have a list of file types not stored in the DB that can be added to the website without a formal deployment?

    Is it possible to stop all uploading of such files and restrict those files to a normal deployment cycle?

    On a side note, the text field used in this forum to submit this post is not formatted properly in Google chrome. Take a look to see what I mean.
  2. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    02 Nov 2009
    Link to this post
    Hi Jeremy,

    Thank you for contacting us and reporting the issue with Google Chrome. 

    Overall you are right for the things you've counted. The only thing that should be touched in the configuration is the cacheDependancy option. Unfortunately there is no way to turn of the file upload entirely for the whole web site. This means that the people working with the web site should be instructed to use only the Images and Documents module. The rest of the things that can be uploaded are custom controls (having extensions .ascx and .cs) as well as master pages and themes (.master). I think that this should not be the case though, in other words, once a web site is put in production such controls and masterpages should not be uploaded anymore, until the next site update. I suggest you performing full site synchronization once you put new versions of the web site, since some of the designers can also include new images or css files. In either way, new controls and master pages should not be deployed when the site is on production stage.  

    Greetings,
    Georgi
    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.
  3. JeremyL
    JeremyL avatar
    3 posts
    Registered:
    27 Oct 2009
    02 Nov 2009
    Link to this post
    Thank you for the reply. So some follow up questions.

    When a control or other file is uploaded through SF into the file system, is that upload registered in the database anywhere? The reason I ask is out setup would probably look something like this

    2 Production Web Servers - Load balanced
    1 Database Server
    1 Staging Server
    Multiple Dev Machines

    So we would put SF into SVN and when a developer or designer want sto add a theme, control, ect, they would check out a new branch in SVN, then when done merge it back to the trunk. Then that would be checked out into staging. After everything was shown as working, it would then be deployed.

    When the deployment happens to the 2 web servers, files are copied, but the database would not be touched unless there was an upgrade, ect. So if when files are uploaded into SF using the system and are put in the normal file system, this setup works great. But if for some reason SF registers that control in the DB even though it's in the file system, then there are more database deployment issues to take into consideration.

  4. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    03 Nov 2009
    Link to this post
    Hello Jeremy,

    Thank you for the follow up. 

    When you upload a new control, Sitefinity registers it only in the web.config file (section <toolboxControls>). It is not registered anywhere in the database. 

    Let me know if you have any other questions. 

    Sincerely yours,
    Georgi
    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.
  5. Lucas
    Lucas avatar
    65 posts
    Registered:
    22 Mar 2010
    25 Mar 2010
    Link to this post
    Is it possible to use somehow the API to catch the ascx upload on the active server and replicate the action on the other servers?

    I mean, let's say we add the control to server 1, it would catch the event and use a synchronization module (webservice for example) to instruct servers 2 and 3 to do the same?
  6. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    25 Mar 2010
    Link to this post
    Hi Lucas,

    Our API does not expose such methods. You could use a third party file replication tool that monitors UserControls folder where the controls are uploaded. Another option would be regulary cheking the files in the directory using standard ASP.NET classes and methods and comparing the files there then replicate then on another folder. Note that this will require to merge the web.condig which is used for a control registration. 

    Greetings,
    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.
Register for webinar
6 posts, 0 answered