0.01
No commit activity in last 3 years
No release in over 3 years
render_static allows you to make your single-page apps (Backbone, Angular, etc) built on Rails SEO-friendly. It works by injecting a small rack middleware that will render pages as plain html, when the requester is one of the most common crawlers/bots out there (Google, Yahoo Baidu and Bing)
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.8.4
~> 3.12
>= 0

Runtime

 Project Readme
= render_static

* http://github.com/herval/render_static

== DESCRIPTION:

render_static allows you to make your single-page apps (Backbone, Angular, etc) built on Rails SEO-friendly. It works by injecting a small rack middleware that will render pages as plain html, when the requester has one of the following user-agent headers:

Googlebot
Googlebot-Mobile
AdsBot-Google
Mozilla/5.0 (compatible; Ask Jeeves/Teoma; +http://about.ask.com/en/docs/about/webmasters.shtml)
Baiduspider
Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)

Please note that, in order for this to work, you need more than one thread/process of your webserver running, as the middleware will effectively make a second call back to your own app and render the content, streaming it back to the requester (crawler/bot).


== TO DO/PROBLEMS:

* Caching support
* Support for other drivers
* Log what's going on

== INSTALL:

Add the following to your Gemfile:

    gem 'render_static'

In order to serve a set of routes as a single-page app, your routes.rb usually contains a catch-all route that will direct /* or /something/* to the same index.html file (the root of your js app). In order to allow the render_static middleware to intercept the right routes, you need to add this to your app initialization:

    render_static.rb
    RenderStatic::Middleware.base_path = "/" # replace / for whichever path matches your app's index.html

render_static will, by default, try to use Firefox as the driver to navigate to content. It will also try to run headlessly - if on a *nix box, you should install xvfb for that to work properly.

And you're done! The middleware will only try to static-render requests made by bots AND that would render application/html content.

You can test that everything is working as expected by CURLing:

    # this will render the usual blank slate client-side apps serve
    curl http://localhost:3000/some/backbone/route

    # this will render a static representation of your page (just like it would look like in a browser)
    curl -A "Googlebot" http://localhost:3000/some/backbone/route