All geek questions in one place

Sitecore web.config and file structure for the READ ONLY production environment

I plan to deploy SiteCore ...

Users can edit content only on server servers .... and I planned DEPLOY to produce only the necessary files and settings necessary for the correct launch of my site ... (Vanilla SiteCore site, deleted from the SiteCore folder ...)

therefore, I assume that I need 100% SiteCoreAssemblies and Config ... more specifically, I was wondering how to remove from the configuration all unused materials necessary for the role of editing web content and content ....

let me know if there are any recommendations / recommendations ... or any recommendations for improving security and deploying a minimal configuration to run will be appreciated ... Thanks Stelio

+6
source share
4 answers

The only reason I'm digging this is because I am doing this in the near future:

See what the " " Configuring the production environment " that @Christian Hagelid pointed out.

More specifically: 1.2.2 Step 2. Clear the solution (optional)

  • Delete unnecessary files Delete the following files:
    • / Indexes folder - If you do not use indexes in your implementation.
    • Everything from the / sitecore folder except: - / service -shell / sitecore.version.xml - / login / default.css - / images
    • /App_Config/Commands.config
    • /App_Config/ConnectionStringsSQLite.config
    • /App_Config/Prefetch/Core.config
    • /App_Config/Prefetch/Master.config
    • /App_Config/Icons.config
    • /App_Config/LanguageDefinitions.config
    • /App_Config/Portraits.config
    • /WebSite/web.config.sqlite *
    • /WebSite/webedit.css
  • Delete or comment on the following sections from the web.config file:
    • Events
    • workflowHistoryStores
    • processors
    • Dataviews
    • pageextenders
    • controlSources
    • Substitutes
    • fastCache for the shell site.
    • watching
    • Teams
    • languageDefinitions
    • the icons
    • portraits
    • publishing house
    • media watchers and config watchers
    • ConfigWatcher from httpModules and system.webServer / modules
    • Defining a file system database from databases
  • Delete or comment on the following scheduled agents in Web.config:
    • CleanupPublishQueue
    • CleanupAgents cleaning intervals should be adjusted if necessary
    • HtmlCacheClearAgent if not used

I urge you to be brave and experiment with settings. Go through the web.config file one at a time and make sure you understand them. I do this periodically to remind myself of the Sitecore features that I don’t use. Try to remove some parameters that you do not need, and when they work, and you are happy with them, share your results.

Take full advantage of caching - Sitecore has great caching options, and if your site is configured correctly quickly, on the other hand, if you set your site caching incorrectly, it can be very slow and have weird problems with dynamic content being cached incorrectly.

Good luck

+6
source

It describes a document called “ Configuring production environments .” It's a bit old, but it can be a good starting point, at least.

Other documentation that may help:

+4
source

You should probably take a look at the Sitecore Security Simplification Guide . It should provide you with a great start to best practices for setting up a secure content delivery system.

+1
source

As far as I remember, the easiest way to do this is actually a license file. Sitecore should be able to provide a "webfarm" license that disables all editing features. There is no manual that I know about folders that you can delete, or sections from the web.config file, and that are likely to have unwanted side effects.

0
source

Source: https://habr.com/ru/post/924744/

More articles:


All Articles