summaryrefslogtreecommitdiff
path: root/users/config/routes.rb
AgeCommit message (Collapse)Author
2013-11-21Refactoring of code, and tests.jessib
2013-11-18Need to cleanup some, but start to show public key for /key/usernamejessib
2013-09-03use the login logout named route instead of sessions resourceAzul
The main part of the sessions resource now lives in the API. the two named routes are just fine for what is left.
2013-09-02Remove references to email_settings controller, which has been removed. An ↵jessib
identities controller will replace it.
2013-07-08Merge branch 'master' into feature/disable_accountjessib
Conflicts: users/app/controllers/users_controller.rb users/app/helpers/users_helper.rb users/app/views/users/edit.html.haml users/app/views/users/show.html.haml users/config/locales/en.yml
2013-07-04user tests -- user update has been moved entirely to api controller, so fix ↵elijah
tests to reflect this.
2013-07-04fix user typeaheadelijah
2013-07-04users engine changes - rewrite of the views, separate email settings to a ↵elijah
separate controller, make users_controller html only and v1/users_controller json only.
2013-07-04new ui - initial user changeselijah
2013-07-03Accounts can be enabled or not. Admins can edit this property.jessib
2013-04-18remove 'api' subdomain restrictionelijah
2013-02-26api for sessions fixedAzul
* now we return the user id on login * allow a destroy request for logging out * added test for api sessions controller
2013-01-29Allow PUT API to update user.jessib
2013-01-22some basic webfinger routes, controller, presenters, viewsAzul
2013-01-16using subdomain for api requests properlyAzul
2013-01-10moved api routes into their own namespaceAzul
In case we need them at some point - now it's new_api_user_path instead of new_user_path for example. This way they should not conflict with the normal route generation
2012-12-17enabled destroying email aliases - no ajax yet.Azul
2012-12-09basic form added to user settings, simple model createdAzul
2012-12-08serve api version 1 in /1/Azul
Just a very simple start for now. Do we want to use the api for the secure remote password auth from js?
2012-11-22basic user edit form and actionsAzul
2012-10-11current_user and authenticate methodsAzul
2012-09-27added in leap web users - one repo to rule them allAzul