Permalink
Browse files

Take advantage or production changes and simplify rackup.ru

  • Loading branch information...
1 parent 8b8ddf5 commit d6e13b061fb080a04f681d0204cea135b823c670 @bmizerany committed Feb 6, 2009
Showing with 7 additions and 16 deletions.
  1. +6 −2 README.markdown
  2. +1 −14 config/rackup.ru
View
@@ -11,12 +11,16 @@ it](http://heroku.com/docs/index.html#_manage_keys_on_heroku)
Now, clone and deploy!
-`projects $ git clone git://github.com/sinatra/heroku-sinatra-app`
+`projects $ wget http://github.com/sinatra/heroku-sinatra-app/tarball/master`
-`projects $ cd heroku-sinatra-app`
+`projects $ tar xzvf sinatra-heorku-sinatra-app-<SHA>.tar.gz`
+
+`projects $ mv sinatra-heroku-sinatra-app-<SHA>/ my_new_app/`
`my_new_app $ heroku create <optional appname> --remote`
+`my_new_app $ mv heroku-sinatra-app.r my_new_app.rb`
+
`my_new_app $ git push heroku master`
Now you may view your site at `http://<appname>.heroku.com`
View
@@ -1,16 +1,3 @@
-require 'rubygems'
-
-# We will need to require Sinatra to gain
-# access to the Sinatra environment for
-# bootstrapping before loading the application
-require 'sinatra'
-
-# This will soon not be needed on Heroku.
-# For now it's important that you set the
-# environment before requiring the application
-# to allow `configure` to work properly
-set :environment, :production
-
# This is for convenice. The defacto Sinatra standard
# is to name your application file after it's parent
# directory
@@ -27,4 +14,4 @@ require "#{parent_directory}/#{application_name}.rb"
disable :run, :reload
# Finally, let's jam!
-run Sinatra::Application
+run Sinatra::Application

0 comments on commit d6e13b0

Please sign in to comment.