Ramaze Google Group

Re: REST resource routes

ashley.mo...@patchspace.co.uk (Ashley Moran) — Fri, 06 Nov 2009 22:27:01 UT

Hmmm, hmmm, hmmm...
How much would everyone here like to be able to use the Merb (RESTful)
router in Ramaze? If there's any demand, I might make a serious stab
at it. When it's not Friday night...
I'm still happy with Merb, but I'm a bit concerned with the lack of
progress due to "Rails 3". I like a lot of things in Ramaze, just not

Re: REST resource routes

clive.cr...@gmail.com (Clive Crous) — Fri, 06 Nov 2009 21:21:20 UT

I agree as well. For our company's RESTful API I have a 90 line
Ramaze::Rewrite dispatcher which I need to modify each time I add a
new resource.
This was the only way to shoehorn REST into Ramaze :(
Clive

Re: REST resource routes

ashley.mo...@patchspace.co.uk (Ashley Moran) — Fri, 06 Nov 2009 20:34:25 UT

I fully agree. I'm not personally too keen on Controller.map
(presumably actually included in either Innate::Node or some other
module - I'm not yet familiar with any of the internals...), although
it's an easy way to get things going.
Thanks for the link. I've never written Rack middleware, so it's

Re: REST resource routes

james.br...@gmail.com (James Britt) — Fri, 06 Nov 2009 19:13:15 UT

I had frustration with the REST code in Ramaze, and decided that the
application should not be concerned with how things get to it.
So I wrote some Rack middleware to handle that.
[link]
It may offer some useful stuff.
Good question.

Re: Implementing long-running jobs in Ramaze

slabou...@gmail.com (Scott LaBounty) — Fri, 06 Nov 2009 14:59:17 UT

Really nice write up. I wish more people would do this sort of thing. It's
great to see (mostly) full applications written up and explained. I love the
code snippets, but seeing how people put things together, really helps.

Scott

--
Scott
[link]

REST resource routes

ashley.mo...@patchspace.co.uk (Ashley Moran) — Fri, 06 Nov 2009 12:04:05 UT

Hi
I tried to write a simple single-resource app the other day to help
with some debugging. I noticed the old REST helper has gone, to be
replaced with contrib/rest
But the new contrib/rest is incomplete. It routes all GET requests to
show, where it needs to route "/resource" and "/resource/1"

Implementing long-running jobs in Ramaze

mwl...@cybrains.net (mwlang) — Fri, 06 Nov 2009 04:50:35 UT

For those of you that are looking for an elegant way to reliably
offload long-running jobs to the background and also report near-
constant feedback back to the user, you may enjoy my most recent blog
on the subject:

[link]

Handling 404s like all other errors...

binarypala...@gmail.com (cult hero) — Thu, 05 Nov 2009 20:04:06 UT

I've been playing with error handling most of the morning and I think
I have a decent idea of how to catch errors via something like this:

Rack::RouteExceptions.route(Ex ception, MainController.r(:error))

Also, in the event someone finds this on a search, the action can
access the exception that's been raised here by "request.env

Re: Live mode doesn't seem to work for me... (but I can't tell!)

binarypala...@gmail.com (cult hero) — Thu, 05 Nov 2009 18:06:43 UT

Well, I figured this out. Don't use "ramaze start" to start an app.
Use start.rb to start it for testing purposes.

Live mode doesn't seem to work for me... (but I can't tell!)

binarypala...@gmail.com (cult hero) — Wed, 04 Nov 2009 21:10:53 UT

I added this "Ramaze.options.mode = :live" to my app.rb file and
restarted my ramaze app via "ramaze start -s thin" and while it seems
to be working exceptions still give me a full trace which leads me to
believe the mode hasn't changed.

What's up?

Re: Deploying Ramaze Controller/Action behind SSL

n...@robinson-wall.com (Nick Robinson-Wall) — Tue, 03 Nov 2009 20:23:34 UT

2009/11/3 Clive Crous <clive.cr...@gmail.com>:
For what it's worth:
I configured my apache (running mod_rails) to listen for https
connections today, it worked without having to make any changes to my
ramaze (2009.10) app which uses #redirect. It automatically redirects
to the login page if you aren't already and the connection stayed

Re: Deploying Ramaze Controller/Action behind SSL

clive.cr...@gmail.com (Clive Crous) — Tue, 03 Nov 2009 10:16:32 UT

2009/11/3 hrnt <aotu...@gmail.com>:
if the incoming connection from Apache/nginx/lighttpd/whatever is SSL
then ramaze works fine.
The problem is that most setups do this:
browser <--SSL--> proxy <--NONSSL--> ramaze
so as far as ramaze is concerned it's "not SSL".
Just be aware of your environment.
Also you don't need to specify "http://.." or "https://" within raw_redirect

Re: Multiple before_all blocks

ashley.mo...@patchspace.co.uk (Ashley Moran) — Tue, 03 Nov 2009 09:37:42 UT

Thanks hrnt
Is this documented? If not, I'll find a space to put it on the wiki
when Michael has signed me up.
I think it's less than ideal though. Two possible improvements spring
to mind:
* allow building up a list of blocks (like RSpec)
* warn when a block is being overridden from a parent class

Re: SitesPoweredByRamaze wiki page

ashley.mo...@patchspace.co.uk (Ashley Moran) — Tue, 03 Nov 2009 09:33:26 UT

That will certainly stop them ;)
Cool thanks, I'll drop it in a private email
Cheers
Ashley

Re: Deploying Ramaze Controller/Action behind SSL

aotu...@gmail.com (hrnt) — Tue, 03 Nov 2009 09:31:11 UT

Ramaze knows about SSL connections if it is running under Passenger
and redirects will work properly. If the incoming connection is with
SSL, "redirect" will redirect to https://

In that case, if you have actions that should only work with SSL, you
should use redirect_raw to force the redirect to use https:// to those