19. Rails (> 2.0.2) or a Rack-based app with a
★
config.ru
Wednesday, March 18, 2009
20. Rails (> 2.0.2) or a Rack-based app with a
★
config.ru
No shell access
★
Wednesday, March 18, 2009
21. Rails (> 2.0.2) or a Rack-based app with a
★
config.ru
No shell access
★
Git only
★
Wednesday, March 18, 2009
22. Rails (> 2.0.2) or a Rack-based app with a
★
config.ru
No shell access
★
Git only
★
Read only filesystem
★
Wednesday, March 18, 2009
23. Rails (> 2.0.2) or a Rack-based app with a
★
config.ru
No shell access
★
Git only
★
Read only filesystem
★
PostgreSQL only
★
Wednesday, March 18, 2009
33. # Have to require sinatra here and force the application name because polyglot
# breaks the auto-detection logic.
gem 'sinatra', '0.9.1' ; require 'sinatra'
Sinatra::Application.app_file = File.join(File.dirname(__FILE__), *%w[.. ..
app.rb])
# Teh App
require Sinatra::Application.app_file
# RSpec
require 'spec/expectations'
# Only including webrat for the tag matcher
require 'hpricot'
require 'sinatra/test'
class TestSession
include Sinatra::Test
# parses whole file on each call
def html
Hpricot(body)
end
end
Wednesday, March 18, 2009
That thing is now a tool for learning rails. I haven’t used it and don’t really intend to.
So, the new heroku.
This makes porting existing apps tricker than you may imagine. For example plugins like paperclip require filesystem access (unless you’ve configured it to use S3). I recommend doing new stuff in Heroku.
This makes porting existing apps tricker than you may imagine. For example plugins like paperclip require filesystem access (unless you’ve configured it to use S3). I recommend doing new stuff in Heroku.
This makes porting existing apps tricker than you may imagine. For example plugins like paperclip require filesystem access (unless you’ve configured it to use S3). I recommend doing new stuff in Heroku.
This makes porting existing apps tricker than you may imagine. For example plugins like paperclip require filesystem access (unless you’ve configured it to use S3). I recommend doing new stuff in Heroku.
This makes porting existing apps tricker than you may imagine. For example plugins like paperclip require filesystem access (unless you’ve configured it to use S3). I recommend doing new stuff in Heroku.
The varnish reverse proxy that sits in front of heroku will cache this for you. It will also cache normal requests with the expires header.