Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tool to properly warmup EpiServer afrer deployment #1

Open
tomaszmadeyski opened this issue Mar 28, 2019 · 2 comments
Open

Add tool to properly warmup EpiServer afrer deployment #1

tomaszmadeyski opened this issue Mar 28, 2019 · 2 comments

Comments

@tomaszmadeyski
Copy link
Contributor

Ideally this tool should warmup (by visiting?) each PageType defined in EpiServer.

@tomaszmadeyski
Copy link
Contributor Author

I've checked how EpiServer (DXC) handles site warmup and according to documentation they use IIS built in tool of applicationInitialization. This assumes that there's a list of urls in the web.config to be visited before site is considered to be ready.

What DXC is doing is that they try to build such list by visiting root page and trying to find (and visit) all relative links which obviously might not be enough. So solution seems to be building such list manually, per project, and putting it into web.config (web config transformation to be specific).

So, my undestanding is that any attempt of doing it from code (this nuget) is meaningless as any code which we will prepare will be run after page is initialized so also after applicationInitialization tool is run.

What are your thoughts @mgrzyb

@kpkozak
Copy link
Contributor

kpkozak commented May 19, 2020

Isn't same functionality achievable using any SmokeTester (even Forte.SmokeTester) during deployment? Do we need to do this on web server side?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants