| # loosely based on: | |
| # http://shiflett.org/blog/2010/jul/auto-increment-with-mongodb | |
| new_id = Mongoid.master["sequences"].find_and_modify | |
| :query =>{"_id"=>"<name of your business entity>"}, | |
| :update=>{"$inc"=>{"seq"=>1}}, | |
| :upsert=>true, | |
| :new =>true #<-- this causes the new incremented id to be returned |
| task :renderview => :environment do | |
| app = YourApp::Application | |
| app.routes.default_url_options = { :host => 'xxx.com' } | |
| controller = YourController.new | |
| view = ActionView::Base.new(app.config.paths.app.views.first, {}, controller) | |
| view.class_eval do | |
| include ApplicationHelper | |
| include app.routes.url_helpers | |
| end | |
| puts view.render(:template => 'your/action') |
| $ cat Procfile | |
| web: rails server thin -p $PORT | |
| $ gem list | grep foreman | |
| foreman (0.19.0) | |
| $ ps aux | grep thin | |
| kmamykin 13773 0.0 0.0 4156 864 pts/2 S+ 14:22 0:00 grep thin | |
| $ foreman start | |
| 14:22:36 web.1 | started with pid 13897 | |
| 14:22:50 web.1 | => Booting Thin | |
| 14:22:50 web.1 | => Rails 3.1.0.rc4 application starting in development on http://0.0.0.0:5000 |
| gem 'rails', '3.1.0.rc5' | |
| gem 'thin' | |
| gem 'foreman' | |
| # Gems used only for assets and not required | |
| # in production environments by default. | |
| group :assets do | |
| gem 'sass-rails', "~> 3.1.0.rc" | |
| gem 'coffee-rails', "~> 3.1.0.rc" |
| gem 'rails', '3.1.0.rc5' | |
| # Gems used only for assets and not required | |
| # in production environments by default. | |
| group :assets do | |
| gem 'sass', '3.1.5' # <= downgraded due to a weird interaction b/w compass blueprint and latest Sass | |
| gem 'sass-rails', "~> 3.1.0.rc" | |
| gem 'coffee-rails', "~> 3.1.0.rc" | |
| gem 'uglifier' | |
| gem 'compass', :git => 'https://github.com/chriseppstein/compass.git', :branch => 'rails31' |
#Introduction
Several layers of css rules:
I hereby claim:
To claim this, I am signing this object:
| /node_modules |
A Pen by Kliment Mamykin on CodePen.
What is prerendering? Pre-rendering a JavaScript heavy website refers to the process of using a proxy that loads the requested page and runs all JavaScript on the page, and then returning the content of the rendered page as the response to the page's request. The advantages of doing so are twofold:
Perfomance of the site is greatly improved as the browser is able to render the page without waiting for external scripts to load and external data api requests to finish. In Brickwork client site that means requesting a store page returns HTML that is already rendered with all the data about the store.
After the initial page HTML is rendered from the response, the browser asycronously request JavaScript scripts that load in the background, query the API for data and re-render the page in browser, adding interactivity to the page. Ideally the page pre-rendered on the server/proxy and the page rendered in the user's browser will be exactly the same (given the api data hasn't chang