On 18. mai. 2009, at 20.41, Naga wrote:
> Any further wisdom to share?
Actually, I suspect this is a cookie issue, since it seems your login
technically works:
> User Update (0.4ms) UPDATE `users` SET `updated_at` = '2009-05-18
> 18:32:19', `remember_token_expires_at` = '2009-06-01 18:32:19',
> `remember_token` = '508e3f5d247d1181e337879685a626b625c5b1e5' WHERE
> `id` = 2
(it updates your user record in the database).
Gitorious sends a session cookie that should be valid in the domain
specified as gitorious_host in config/gitorious.yml. In my setup, I
use "gitorious.local" as the Gitorious host, this means that Gitorious
sends a session cookie with the domain ".gitorious.local"; this would
be useless if I entered "localhost" in my browser.
What I did is:
- add an entry for gitorious.local to 127.0.0.1 in /etc/hosts (if
you're on Windows, it's probably in C:\System32\drivers\etc\hosts)
- use gitorious.local at gitorious_host in config/gitorious.yml:
development:
gitorious_host: gitorious.local
- point my browser to http://gitorious.local:3000/
If you need to check which domain the cookie is set for, most browsers
have an option to ask you for confirmation each time the browser
receives a cookie. Check the domain part of the cookie to see what's
sent.
Good luck!
- Marius
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gitorious?hl=en
-~----------~----~----~----~------~----~------~--~---
