The Wayback Machine - https://web.archive.org/web/20201130092010/https://github.com/GoogleChrome/rendertron/issues/393
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

Create best practices documentation #393

Open
AVGP opened this issue May 7, 2020 · 2 comments
Open

Create best practices documentation #393

AVGP opened this issue May 7, 2020 · 2 comments

Comments

@AVGP
Copy link
Collaborator

@AVGP AVGP commented May 7, 2020

Right now, there is no "docs/best_practices.md" file.
Create this file and describe the best practices for running Rendertron. Some to get started:

  • Run Rendertron behind a firewall or proxy with authentication, because it does not provide an authentication layer.
  • Enable caching to speed up the response times
  • Regularly pre-warm the cache by requesting a render for your most important URLs to make sure that bots get a quick response
@hheexx
Copy link

@hheexx hheexx commented Jul 12, 2020

I recommend running rendertron at reverse proxy level, not using middleware.
Because if you use it as middleware and you have reverse proxy in front of it you can not cache pages without having bot detection logic in reverse proxy. If you have bot detection logic in reverse proxy then it makes sense to have it only there for clear separation of concerns. Duplicate code is always pain.

Comments?

we should add link in readme to good nginx config for example this one https://gist.github.com/justindavies/7421d1f112f5c1b606dd27f4fcd8a856#file-nginx-rendertron-conf

@AVGP
Copy link
Collaborator Author

@AVGP AVGP commented Jul 13, 2020

We do have new docs coming - you can take a look at it in the docs folder.
That contains an nginx example and I'd love to see if you have improvements to that :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.