leap_web.git - [leap

Age	Commit message (Collapse)	Author
2013-11-18	Need to cleanup some, but start to show public key for /key/username	jessib

2013-09-03	use the login logout named route instead of sessions resource	Azul
	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-02	Remove references to email_settings controller, which has been removed. An ↵	jessib
	identities controller will replace it.
2013-07-08	Merge branch 'master' into feature/disable_account	jessib
	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-04	user tests -- user update has been moved entirely to api controller, so fix ↵	elijah
	tests to reflect this.
2013-07-04	fix user typeahead	elijah

2013-07-04	users 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-04	new ui - initial user changes	elijah

2013-07-03	Accounts can be enabled or not. Admins can edit this property.	jessib

2013-04-18	remove 'api' subdomain restriction	elijah

2013-02-26	api for sessions fixed	Azul
	* now we return the user id on login * allow a destroy request for logging out * added test for api sessions controller
2013-01-29	Allow PUT API to update user.	jessib

2013-01-22	some basic webfinger routes, controller, presenters, views	Azul

2013-01-16	using subdomain for api requests properly	Azul

2013-01-10	moved api routes into their own namespace	Azul
	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-17	enabled destroying email aliases - no ajax yet.	Azul

2012-12-09	basic form added to user settings, simple model created	Azul

2012-12-08	serve 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-22	basic user edit form and actions	Azul

2012-10-11	current_user and authenticate methods	Azul

2012-09-27	added in leap web users - one repo to rule them all	Azul