sinatra

When I try to do this in Sinatra, class Comment include DataMapper::Resource property :id, Serial property :body, Text property :created_at, DateTime end get '/show' do comment = Comment.all @comment.each do |comment| "#{comment.body}" end end It returns this error, ERROR: undefined method `bytesize' for #<Comment:0x13a2248> Could anyone point me to the right direction? Thanks, Luke Antins Your getting this error because Sinatra takes the return value of a route and converts it into a string before trying to display it to the client. I suggest you use a view/template to achieve your goal: #

(Disclaimer: New to deploying Sinatra on Heroku.) I have seen http://www.sinatrarb.com/configuration.html and it tells me to set :environment, :production . My question is, how can I specify it to do: "when in Heroku, set environment as production, else stay in test/development." Also, even after putting the line set :environment, :production , I don't think it is working because when I try to rackup the app locally, it's still running (when I know (or I think I know) that it shouldn't because I haven't installed postgres on my computer). Gemfile group :production do gem 'dm-postgres-adapter'

Is there a way to default a parameter in Sinatra? I am currently looking to see if 'start' was passed as a parameter, but it seems a little hacky. It would be nice if I could tell Sinatra to default certain parameters if they are not specified. get '/comments/?' do # want to setup page stuff, default to first page if not specified params[:start] = 0 if !params[:start] end Any ideas? It's true that you can use ||= in this way, but it's a very strange thing to set the params after retrieving them. It's more likely you'll be setting variables from the params. So instead of this: params[:start] ||

I am using this code to enable logging in my Sinatra app: log_file = File.new('my_log_file.log', "a") $stdout.reopen(log_file) $stderr.reopen(log_file) $stdout.sync=true $stderr.sync=true The actual logging is done using: logger.debug("Starting call. Params = #{params.inspect}") It turns out that only INFO or higher level log messages are logged and DEBUG messages are not logged. I am looking for a way to set up the log level to DEBUG. I guess there might be a better way, but you can always do something like setting the log level in a before filter: before do logger.level = 0 end You can set

This question already has an answer here: What is the community-preferred Ruby unit testing framework? 4 answers Are the same unit testing frameworks used for different web frameworks - Rails, Merb, Sinatra, Ramaze and desktop frameworks - Shoes? And what is the most widely used unit testing framework that would work with all of the various web and desktop frameworks? TestUnit is based on JUnit, and so there is port to most languages. This is probably the most ubiquitous. Behavior driven testing has yielded tools like RSpec, and it seems like right now that may be the most popular test

I'm writing a simple app that takes standard input from the user. As for the email entry, I have it verify if it is in a standard email format and then have it list the problems like this when a new instance is going to be saved: u = User.new u.email = params[:email] u.save if u.save redirect '/' else u.errors.each do |e| puts e end end I know that if it is correct it should return back to the home page. If it is wrong I want it to return to the home page as well, but I want it to return an error value (so I can have a pop-up or just something onscreen letting the user know that the format of

I'm trying to create a route with Sinatra that only accepts POST with an Content-type: application/json without success. My approach is as follows: post '/dogs', :provides => :json do # returns here a json response end Testing with curl, I have seen that :provides => :json configures the route to respond with an Content-Type: application/json . That's right because I want also to respond with a JSON message to the POST request but I really need that this route only respond to POST requests with a Content-Type: application/json and not, for example, to others (e.g. Content-Type: application/xml