For the sign_out url you should have DELETE method.
If you run 'rake routes' inside your project path, you could see this
route, and there is no GET /users/sign_out at all, only DELETE /users/
sign_out.
So you should use some mechanisme to make <%= link_to "Sign out",
destroy_user_session %> = Sign
You can have a short-look at OAuth2 protocol, it's simple but should
have many implementations on ruby.
Here is http://tools.ietf.org/html/draft-ietf-oauth-v2-20 really
boring doc, but once you have read it, you'll know everything about
this secret/keys ;)
On Jul 20, 9:58 am, John Senthil wrote:
Sad(( is here nobody use postgresql with rails? Or I'm asking
something wrong?
On 18 май, 17:15, sleepwalker wrote:
> Does Rails 3 support native working withpostgresqlschemas, or I
> should try some own solution?
>
> I have some already-createdpostgresqldatabase with 4 or somt
Does Rails 3 support native working with postgresql schemas, or I
should try some own solution?
I have some already-created postgresql database with 4 or somth
schemas.
By putting "schema_search_path: ejabber, public, admin, statistic"
into database.yml I told Rails that I have more than 1 schema.
Does Rails 3 support native working with postgresql schemas, or I
should try some own solution?
I have some already-created postgresql database with 4 or somth
schemas.
By putting "schema_search_path: ejabber, public, admin, statistic"
into database.yml I told Rails that I have more than 1 schema.
Sorry for the newb question,
but it is: going through first steps I fond this exception.
Have no idea, my rails version is 2.3.5
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@google
6 matches
Mail list logo
