Available integrations
- 16 Apr 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Available integrations
- Updated on 16 Apr 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Prerender.io is a 100% server side component, so technically it doesn't matter what frontend framework you have, the only thing that matters is the way you serve your static files, such as HTML, JS, CSS and so on.
Your JavaScript application may be served in various ways, for example using a Node.js (Express.js) server, or Apache, NGINX, Java Spring, IIS, or cached by a CDN such as Cloudflare. The only thing you need to do is to find the middleware or configuration example for your backend, set it up, and you're good to go.
After Signing up you will get your Prerender token if you don't have one yet.
Integration guide line
To ensure that Prerender is working as expected, it's important to integrate it into the part of your system that handles incoming web requests.
You can easily do this through common integration points like:
- Frontend Servers (such as Apache or NGINX),
- Content Delivery Networks (CDNs),
- or Reverse Proxy Servers.
By integrating Prerender into these components, it can capture and prerender pages in response to web requests.
Prerender.io officially maintained middleware:
- Node(Express.js)
- Node(Nuxt.js)
- Rails (Ruby)
- Nginx
- Apache
- IIS
- Cloudflare
- Docker
- Firebase (with Cloudflare)
- Magento2
Community maintained middleware:
- Spring (Java)
- ASP.NET MVC (C#)
- Zend Framework2 (PHP)
- Symfony 2 (PHP)
- Laravel (PHP)
- Tornado (Python)
- Django (Python)
- Spray (Scala)
- Koa (Javascript)
- Hapi (Javascript)
- HAProxy
- CloudFront
- Netlify
- Akamai
Other integrations:
Was this article helpful?