The Camping web micro-framework for Ruby. ()

headers Magnus Holm | 3 Jul 2008 02:52 · /dispatch.cgi/

_______________________________________________
Camping-list mailing list
Camping-list@...
http://rubyforge.org/mailman/listinfo/camping-list
On Thu, Jul 03, 2008 at 02:52:41AM +0200, Magnus Holm wrote:
> Come on, you lazy interrogative! Are your shoes too heavy? 

Bzzt!  (Drawing on backup camping power grids...)  Very sorry to be
bad about this.  Yeah, lots of Shoes stuff going on this week as
we're shooting for a July 31st release and there many bothersome bugs
to smash.

You've all done a lot of fanastic work and I say we keep working a
bit longer.  I just merged zimbatm's week-old patches and I think it
would be great if we could get more campers to mess with judofyr's
gems, as I think camping 2.0 will inspire some breakages.

Augusttime would be better for me, but let's talk about what you
guys want to do.

_why

Hi all,

I have a little camping micro-blog that's working well with the cookie
session store, but falls over when I try to use the AR session store.
The changes I made were:

require 'camping/session' becomes require 'camping/ar/session'

module Blog; include Camping::Session; end becomes module Blog;
include Camping::ARSession; end

and I did the create_schema in Blog.create.

It set up the session table correctly, it adds a new row with a
session id and sets a cookie on the browser correctly, but it never
saves anything to the session state hash.  Do I need to do something
differently to make  <at> state save itself?  Using the cookie session
store, changes are saved anytime I do something to  <at> state, which is
how I would expect it to work.

I'm using the latest version from why's git repo with the default sqlite setup.

Thanks!
Josh

Specifically, Dreamhost.  I'm trying to figure out how to get this to
work the standard dispatch.cgi or dispatch.fcgi setup.  I've been
using the instructions that Magnus sent out when he first announced
his plan for Camping 2.0, but they either no longer apply, or I'm an
edge case.

I've been pushing at it for a while, just to get it working on CGI,
and the problem seems to be that dispatch.cgi doesn't end in .ru!
Rack tries to "require 'dispatch.cgi'", which is no good.  Here's my
dispatch.cgi, with names changed to protect the innocent:

==================

#!/usr/bin/env rackup

ENV['GEM_PATH'] = '/path/to/local/gems'
ENV['GEM_HOME'] = '/path/to/local/gems'
ENV['FORCE_ROOT']=1.to_s

Dir.chdir '/path/to/app'

require 'app'
App::Models::Base.establish_connection :adapter => 'sqlite3',
:database => 'app.db'
App.create

run App

=============

And the error trace, as reported through apache's error logs:

/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no such file to load -- dispatch.cgi
(LoadError)
  from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
  from /usr/lib/ruby/gems/1.8/gems/rack-0.3.0/bin/rackup:92
  from /usr/bin/rackup:19:in `load'
  from /usr/bin/rackup:19
Premature end of script headers: dispatch.cgi

I'm still trying to get my head around the new Rack setup, the problem
might be some simple naivete on my part.  Anyone have any ideas how I
can push forward?

Thanks,
Eric

Some progress: I put most of the code from dispatch.cgi into a
"config.ru", and dispatch.cgi now uses backticks to literally call
'/usr/bin/env rackup'.  This works, yet now calls to "/" redirect to
"/dispatch.cgi/" (this is truly the path in my browser location bar),
and it messes with my routing.

====  config.ru  ======
Dir.chdir '/path/to/app'
require 'app'
App::Models::Base.establish_connection :adapter => 'sqlite3',
:database => 'app.db'
App.create
run App

==== dispatch.cgi  ====
#!/usr/bin/ruby
ENV['GEM_PATH'] = '/path/to/gems'
ENV['GEM_HOME'] = '/path/to/gems'
puts `/usr/bin/env rackup`

And now I am definitely giving up for the night and sleeping.  Any ideas?

Thanks,
Eric

On Fri, Jul 11, 2008 at 1:06 AM, Eric Mill <kprojection@...> wrote:
> Specifically, Dreamhost.  I'm trying to figure out how to get this to
> work the standard dispatch.cgi or dispatch.fcgi setup.  I've been
> using the instructions that Magnus sent out when he first announced
> his plan for Camping 2.0, but they either no longer apply, or I'm an
> edge case.
>
> I've been pushing at it for a while, just to get it working on CGI,
> and the problem seems to be that dispatch.cgi doesn't end in .ru!
> Rack tries to "require 'dispatch.cgi'", which is no good.  Here's my
> dispatch.cgi, with names changed to protect the innocent:
>
> ==================
>
> #!/usr/bin/env rackup
>
> ENV['GEM_PATH'] = '/path/to/local/gems'
> ENV['GEM_HOME'] = '/path/to/local/gems'
> ENV['FORCE_ROOT']=1.to_s
>
> Dir.chdir '/path/to/app'
>
> require 'app'
> App::Models::Base.establish_connection :adapter => 'sqlite3',
> :database => 'app.db'
> App.create
>
> run App
>
> =============
>
> And the error trace, as reported through apache's error logs:
>
> /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
> `gem_original_require': no such file to load -- dispatch.cgi
> (LoadError)
>  from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
>  from /usr/lib/ruby/gems/1.8/gems/rack-0.3.0/bin/rackup:92
>  from /usr/bin/rackup:19:in `load'
>  from /usr/bin/rackup:19
> Premature end of script headers: dispatch.cgi
>
> I'm still trying to get my head around the new Rack setup, the problem
> might be some simple naivete on my part.  Anyone have any ideas how I
> can push forward?
>
> Thanks,
> Eric
>

_______________________________________________
Camping-list mailing list
Camping-list@...
http://rubyforge.org/mailman/listinfo/camping-list
Actually, that is what I'm doing now, and I'm still seeing the same
behavior -- redirects preface the URL with "/dispatch.cgi/", and the
Camping cookies are valid under path "/dispatch.cgi/".  I have another
camping app on the same account, that uses Camping 1.5.180, and when I
first tried it under CGI I didn't get this behavior.  I'm using the
same .htaccess, too.

-- Eric

On Mon, Jul 14, 2008 at 4:44 AM, Magnus Holm <judofyr@...> wrote:
> What about dropping the idea of config.ru and just create a dispatch.cgi
> like this?
>
>     #!/usr/bin/env ruby
>     require 'app'
>     Rack::Handler::CGI.run(App)
>
> On Fri, Jul 11, 2008 at 7:33 AM, Eric Mill <kprojection@...> wrote:
>>
>> Some progress: I put most of the code from dispatch.cgi into a
>> "config.ru", and dispatch.cgi now uses backticks to literally call
>> '/usr/bin/env rackup'.  This works, yet now calls to "/" redirect to
>> "/dispatch.cgi/" (this is truly the path in my browser location bar),
>> and it messes with my routing.
>>
>> ====  config.ru  ======
>> Dir.chdir '/path/to/app'
>> require 'app'
>> App::Models::Base.establish_connection :adapter => 'sqlite3',
>> :database => 'app.db'
>> App.create
>> run App
>>
>> ==== dispatch.cgi  ====
>> #!/usr/bin/ruby
>> ENV['GEM_PATH'] = '/path/to/gems'
>> ENV['GEM_HOME'] = '/path/to/gems'
>> puts `/usr/bin/env rackup`
>>
>>
>> And now I am definitely giving up for the night and sleeping.  Any ideas?
>>
>> Thanks,
>> Eric
>>
>> On Fri, Jul 11, 2008 at 1:06 AM, Eric Mill <kprojection@...> wrote:
>> > Specifically, Dreamhost.  I'm trying to figure out how to get this to
>> > work the standard dispatch.cgi or dispatch.fcgi setup.  I've been
>> > using the instructions that Magnus sent out when he first announced
>> > his plan for Camping 2.0, but they either no longer apply, or I'm an
>> > edge case.
>> >
>> > I've been pushing at it for a while, just to get it working on CGI,
>> > and the problem seems to be that dispatch.cgi doesn't end in .ru!
>> > Rack tries to "require 'dispatch.cgi'", which is no good.  Here's my
>> > dispatch.cgi, with names changed to protect the innocent:
>> >
>> > ==================
>> >
>> > #!/usr/bin/env rackup
>> >
>> > ENV['GEM_PATH'] = '/path/to/local/gems'
>> > ENV['GEM_HOME'] = '/path/to/local/gems'
>> > ENV['FORCE_ROOT']=1.to_s
>> >
>> > Dir.chdir '/path/to/app'
>> >
>> > require 'app'
>> > App::Models::Base.establish_connection :adapter => 'sqlite3',
>> > :database => 'app.db'
>> > App.create
>> >
>> > run App
>> >
>> > =============
>> >
>> > And the error trace, as reported through apache's error logs:
>> >
>> > /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
>> > `gem_original_require': no such file to load -- dispatch.cgi
>> > (LoadError)
>> >  from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
>> > `require'
>> >  from /usr/lib/ruby/gems/1.8/gems/rack-0.3.0/bin/rackup:92
>> >  from /usr/bin/rackup:19:in `load'
>> >  from /usr/bin/rackup:19
>> > Premature end of script headers: dispatch.cgi
>> >
>> > I'm still trying to get my head around the new Rack setup, the problem
>> > might be some simple naivete on my part.  Anyone have any ideas how I
>> > can push forward?
>> >
>> > Thanks,
>> > Eric
>> >
>> _______________________________________________
>> Camping-list mailing list
>> Camping-list@...
>> http://rubyforge.org/mailman/listinfo/camping-list
>
>
>
> --
> Magnus Holm
> _______________________________________________
> Camping-list mailing list
> Camping-list@...
> http://rubyforge.org/mailman/listinfo/camping-list
>

Could you show us the .htaccess please? :)

Also, is it possible that you could simply rename dispatch.cgi to  
something like 'appname' and use htaccess to grant that file cgi  
execution type permissions? Or does this need to be on the root of a  
domain?

can you please try adding to htaccess SetEnv SCRIPT_NAME /path/to/app

Assuming your dispatch is in /path/to/app/dispatch.cgi

Let us know what happens!

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31

1	May 2013
1	April 2013
17	March 2013
2	February 2013
9	January 2013
3	December 2012
3	September 2012
43	August 2012
2	June 2012
55	May 2012
154	April 2012
76	March 2012
11	February 2012
12	January 2012
89	December 2011
17	November 2011
69	October 2011
14	September 2011
46	August 2011
6	July 2011
6	June 2011
9	May 2011
1	March 2011
10	February 2011
17	January 2011
6	December 2010
5	November 2010
14	October 2010
104	August 2010
65	July 2010
99	June 2010
11	May 2010
31	April 2010
27	March 2010
5	February 2010
11	January 2010
3	December 2009
22	November 2009
44	October 2009
5	September 2009
19	August 2009
13	July 2009
41	June 2009
31	May 2009
11	April 2009
8	March 2009
26	February 2009
13	January 2009
6	December 2008
16	November 2008
13	October 2008
4	September 2008
19	August 2008
58	July 2008
44	June 2008
113	May 2008
5	April 2008
18	March 2008
15	February 2008
11	January 2008
3	December 2007
36	November 2007
37	October 2007
75	September 2007
13	August 2007
21	July 2007
19	June 2007
46	May 2007
34	April 2007
17	March 2007
11	February 2007
42	January 2007
3	December 2006
39	November 2006
6	October 2006

Re: Getting rid of the route maker

Re: Getting rid of the route maker

AR Sessions

Troubleshooting: Camping 2.0 on CGI on a shared host

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

Re: Troubleshooting: Camping 2.0 on CGI on a shared host