similar to: multipart/form-data support for Camping Apache/FastCGI

Okay, I have tested mounting several of my apps under Lighttpd and Apache, both running FastCGI. I''m going to explain the configuration, but first: update. gem install camping --source code.whytheluckstiff.net == Mounting Root for Lighttpd+FastCGI == server.port = 3045 server.bind = "192.168.0.103" server.modules = (

Hello all, I am running in some little stumbling blocks with passenger as a multi user environment (the most problematic feature is that, once you setup a sub-domain passenger wants you to declare on nginx every app running on that nginx server which is not ideal to add apps on the fly and / or if a user wants to run 2 apps from his space) so I was thinking about a more drag a drop / one line

Just up: gem install camping --source code.whytheluckystiff.net The changes: * Both bin/camping and Camping::FastCGI.serve now act according to the Camping Server specification.[1] * Docs are complete. _why [1] https://code.whytheluckystiff.net/camping/wiki/TheCampingServer

Hi, I have built a simple Camping application which indexes an ODBC datasource using Ferret on startup, then accepts search strings and renders the resulting hit list in HTML, and it works quite nicely. The next step was to alternately render the list in XML for consumption by another application. In Rails, I would simply use Builder in the view to get the job done, and so I did the same in

Hi everybody, I would like to use ruby2ruby in a caming project, but there seems to be an incompatibility with camping, ruby2ruby and markaby. Unfortunately I receive strange Markaby::InvalidXhtmlErrors. To demonstrate, that only combination of all three components causes the problem I added the following code. I relies on Markaby and ruby2ruby only and works fine (a.k.a. as expected).

Dear camping users, having been contacted by Julian Tarkhanov, I am willing to prepare the next camping release. _why has given me his friendly approval, with the reserve that camping.rb should be lower than 4k. He also told me that he wanted to remove the ActiveSupport and Markaby dependencies. I am writing here to get the users input so that I don''t do any mistake. So far, my plans

Dan did you get camping running on dreamhost already?? i?m trying to run it also but i haven''t succeed yet. it runs on command line but when i add the rewrite rules on .htaccess i get a internal server error. I emailed support to ask about ScriptAlias and they say they cannot change or add that to apache conf. -- Andr? G. Cardozo

Camping now comes with a sessioning class, checked in tonight. To get sessions working for your application: 1. require ''camping/session'' 2. include Camping::Session in your application''s toplevel module. 3. In your application''s create method, add a call to Camping::Models::Schema.create_schema 4. Throughout your application, use the @state

hi all, curious about your input on this latest design experience i''ve had with camping. none of that developing a traditional html ui, a ruby backend, and ajax-ifying the application after being built. - i started straight off with a camping-based json api (for the model). - next step was writing the controller in pure js - no dom interactions here. - then finishing off with a view

Not too different from their corresponding last releases, but documentation has been filled in for both. To upgrade: gem install camping --source code.whytheluckystiff.net And, here is a complete changelog: == Camping 1.5 * Camping::Apps stores an array of classes for all loaded apps. * bin/camping can be given a directory. Like: <tt>camping examples/</tt> * Console mode -- thank

Hi, Camping 1.5.180 Ruby 1.8.6 It looks like Camping is choking on the ''rows'' attribute for input tags: input(:name => ''cuid'', :type => ''text'', :size => 10, :rows => 3) That will fail with: Markaby::InvalidXhtmlError no attribute `rows'' on input elements:

Getting Camping to work with FastCGI is a little clunky, since FastCGI doesn''t really understand mounting apps and sometimes the environment vars are a little whack. To keep the postambles easy to read, I''ve moved the handy stuff into lib/camping/fastcgi.rb. == Mounting a Single App Assuming: Camping.goes :Blog ... this goes in your postamble ... require

Hi Folks, I''ve been trying to get camping up and running on dreamhost for the past six hours, but have had no success. I''d really appreciate any suggestions! The camping gem is on the dreamhost server, but just to make sure it wasn''t a dependency issue causing all the problems, I installed camping + the full set of dependencies in my own gem directory (both are on the

Hi, I made some experiments with the sample blog application, my index.fcgi file contains the following: require ''camping/fastcgi'' Camping::Models::Base.establish_connection( :adapter => ''sqlite3'', :database => ''database/camping.db'' ) Camping::FastCGI.serve(''blog.rb'') Without ScriptAlias the application works fine,

{} || || ~~~~~~~~~~~~~~~ <= _whycake ~ Camping 2.1 ~ ~~~~~~~~~~~~~~~ I''m pleased to announce another release of Camping, the microframework. This time we''ve focused on improving the 1.9 support, adding (builtin) support for more template engines, refreshing the homepage and just general bug fixes. gem install camping Home:

Hi, I''ve got multipart request with 1 file upload form problem. I''m using suse 10 basic installation : -ruby 1.8.2, -rubyfcgi 0.8.6-5, -apache 2.0.54, -apache2-mod_fastcgi-2.4.2-4 When starting whith webrick, my application uploads files correctly.When using both cgi or fastcgi, browser runs forever with files greater than 5kb. fastcgi

Consider this Camping 1.5 pre-release. gem install camping --source code.whytheluckystiff.net Look for: * The new Markaby features. <http://redhanded.hobix.com/inspect/lessMethod_missingInMarkaby.html> <http://redhanded.hobix.com/inspect/markabySMagicPermeationBranch.html> * The Camping::FastCGI class. * R(C, ...) properly escapes wacky arguments. _why

in one of my recent email, I add .to_s to PATH_INFO in camping code. actually, this is probably very wrong. the problem is probably something like PATH_INFO does not exist when using FastCGI. I have not done all my homework, but so far what I found is lighttpd has a special option "broken-scriptfilename": breaks SCRIPT_FILENAME in a wat that PHP can extract PATH_INFO from it (default:

Hey Folks, I''m deploying a camping app on an internal Apache2 + FastCGI server at my office. Of course, on my Mac it works great, but I can''t get things to work with Apache and FCGI. I''ve followed the directions on why''s page documenting how to do this, but I''m getting the following error in my Apache error.log file: FastCGI: (dynamic) server

I''m getting into camping in a big way--I love that you can put together full-fledged apps with so little code and overhead. Does anyone know of any documentation about getting Camping apps running on Media Temple''s GridServer? Of course I''ve found the Camping server page[1], but I can''t work out how to associate running camping apps with a (sub)domain