Try our conversational search powered by Generative AI!
AI OnAI Off
Episerver without the admin parts
Hello Andreas what you have described is similar to the future vision of the platform as described here: https://world.episerver.com/blogs/martin-ottosen/dates/2019/12/asp-net-core-beta-program/
If its of interest you can apply to join the closed beta programme for the future version of the platform here: https://world.episerver.com/service-and-product-lifecycles/aspnetcore/
Feb 02, 2020 20:00
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Usually I see infrastructure with a Episerver admin server within a DMZ and X number of front servers which are public. The front servers are usually "equal" to the admin server, except for restricting access to the admin interface. This seems like a wierd solution - to include the admin parts but to restrict access to it. It would sound more rational to not include the admin parts at all (and therefore not having to restrict stuff). A nice solution would be to have one development project for the front server, and another project for the admin server which reference the front server project and just adds the admin parts.
So, in an attempt to try my theory in practice, I started removing the *.UI nuget packages. However, I couldn't get far before I noticed some packages required me to keep many of the UI packages - for example EPiServer.CMS.UI.AspNetIdentity and EPiServer.Find.Cms, so I gave up.
Did anyone of you ever attempt to create a site truly without any admin stuff? I would assume that this solution would also be slightly better performant.