| Age | Commit message (Collapse) | Author |
|---|
|
|
|
admins) or stay as a nested resource for a particular user (for normal users and when you visit the tickets list of a particular user).
|
|
|
|
|
|
separate controller, make users_controller html only and v1/users_controller json only.
|
|
validation.
|
|
|
|
|
|
|
|
localization.
|
|
|
|
|
|
can't get it working.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Token auth with a database of it's own
|
|
Bugfix/2298 fix couchdb view
|
|
|
|
|
|
|
|
|
|
|
|
adding view of pgp key by login or email aliases
|
|
|
|
|
|
Couch uses partly random partly sequential ids by default. We could
change that in couch config to be all random. But this is probably more
safe.
|
|
|
|
|
|
fetch secret token for signing cookies from config
|
|
catch Errno's and RestClient errors and throw a more meaningful error
|
|
Allow getting salt and proper error messages for invalid login attempts
|
|
make sure only our own models are loaded
|
|
This is just a quick hack. we should move all engines to a dir of their own.
|
|
* The APP_CONFIG needs to be initialized in core so that is required from other engines
* paths for load_views need to be relative to the model - not to rails root.
|
|
|
|
|
|
|
|
|
|
|
|
Migration flow for couch db
|
|
INSTALL is mostly for development and we do not include couch security advices in there
|
