| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-09-19 | Merge pull request #85 from azul/refactor/user_account_shortcut | jessib | |
| user.account shortcut to Account.new(user) | |||
| 2013-09-18 | user.account shortcut to Account.new(user) | Azul | |
| 2013-09-18 | Merge pull request #83 from jessib/feature/billing_admin_cancel_subscriptions | azul | |
| Feature/billing admin cancel subscriptions | |||
| 2013-09-17 | We don't want billing active in development environment. | jessib | |
| 2013-09-17 | This doesn't actually run any tests, but at least includes what we might ↵ | jessib | |
| want to test regarding subscriptions. | |||
| 2013-09-12 | Merge pull request #81 from leapcode/master | jessib | |
| Version 0.2.2 | |||
| 2013-09-11 | Version 0.2.20.2.2 | Azul | |
| 2013-09-09 | First run at having admins cancel user subscriptions. | jessib | |
| 2013-09-05 | Merge pull request #80 from azul/bugfix/fix-tests-broken-by-route-removal | azul | |
| use /login instead of /sessions/new and test successful login | |||
| 2013-09-04 | switch submodule to use https:// instead of git:// - NOTE: this requires you ↵ | Micah Anderson | |
| do a git submodule sync | |||
| 2013-09-04 | use /login instead of /sessions/new and test successful login | Azul | |
| 2013-09-04 | fix login form - use api session url | Azul | |
| There's no non api sessions resource anymore. | |||
| 2013-09-03 | Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly | jessib | |
| Bugfix/3623 teardown test data properly | |||
| 2013-09-03 | Merge pull request #75 from azul/feature/token-expiry | jessib | |
| Token expiry | |||
| 2013-09-03 | Merge pull request #76 from azul/feature/3600-visual-feedback-on-failed-signup | jessib | |
| Ensure json requests get json error response on failure | |||
| 2013-09-03 | Merge pull request #79 from azul/cleanup/remove-outdated-controller-actions | jessib | |
| Cleanup/remove outdated controller actions | |||
| 2013-09-03 | clearify usage of V1::UsersController#index for autocomplete | Azul | |
| [skip ci] | |||
| 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-03 | remove email aliases controller - we don't use it anymore | Azul | |
| 2013-09-03 | Cleanup sessions controller - webapp logs in through the api. | Azul | |
| So the #create and #update actions were not needed anymore. Also removed the tests | |||
| 2013-09-03 | remove unneccessary user creation and destruction in ticket test | Azul | |
| 2013-09-03 | remove the user after integration testing customer creation | Azul | |
| 2013-09-03 | different tests need different names | Azul | |
| 2013-09-03 | do not leave behind users in billing unit and functional tests | Azul | |
| 2013-09-03 | Account: Composition to handle User and its identities | Azul | |
| We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests). | |||
| 2013-09-03 | cleanup records after running user integration tests | Azul | |
| 2013-09-03 | simplify users_controller_test | Azul | |
| 2013-09-03 | don't leave id records behind when unit testing | Azul | |
| 2013-09-03 | expire token according to config setting auth:token_expires_after | Azul | |
| 2013-09-03 | use Token#authenticate for authentication | Azul | |
| This will return the user. But we can add timestamp validations and updates here. | |||
| 2013-09-03 | integration test for displaying internal server error during signup | Azul | |
| 2013-09-03 | Test the error handling of json and html responses | Azul | |
| 2013-09-03 | Ensure json requests get json error response on failure | Azul | |
| Normally rails sends an html page which can't be parsed by the client. | |||
| 2013-09-02 | Merge pull request #78 from jessib/finish_removing_email_settings_references | azul | |
| Remove references to email_settings controller, which has been removed. ... | |||
| 2013-09-02 | Remove references to email_settings controller, which has been removed. An ↵ | jessib | |
| identities controller will replace it. | |||
| 2013-09-02 | Merge pull request #77 from azul/feature/3522-configurable-logfile | jessib | |
| add config setting for logfile | |||
| 2013-09-02 | Merge pull request #74 from azul/refactor/finding-users | jessib | |
| there's no need for User#find_by_param. clean it up | |||
| 2013-09-02 | document the logfile option in the defaults.yml | Azul | |
| 2013-09-02 | add config setting for logfile | Azul | |
| This is the most simple thing that could possibly work. If you do not specify a :logfile in your environments config Rails will use the default. | |||
| 2013-08-30 | also replace find_by_param in billing engine | Azul | |
| 2013-08-30 | there's no need for User#find_by_param. clean it up | Azul | |
| 2013-08-27 | Not ideal way to do it, but was proving complicated to have a config file ↵ | jessib | |
| specify which gems for which environments. Here, we have the billing gem included for the development and test environments only, hardcoded in the Gemfile. Then we show the links to billing based on a config file setting. The setting itself could be used to specify different types of billing, but isn't yet. | |||
| 2013-08-27 | Merge branch 'master' into billing_with_tests | jessib | |
| 2013-08-27 | Merge pull request #72 from azul/feature/token-based-auth | jessib | |
| Feature: Token based auth | |||
| 2013-08-27 | refactor: Changing the py test to use less globals and session only locally. | Azul | |
| 2013-08-27 | use token to update user password | Azul | |
| 2013-08-27 | separate different tests for showing non existant user | Azul | |
| This way the failed stubbing errors were more telling | |||
| 2013-08-27 | token.user will get you the right user | Azul | |
| This way we can stub the token to return the user directly. Stubbing User.find_by_param is not a good idea as it will make all calls to User#find_by_param with a different id fail. | |||
| 2013-08-27 | do not redirect if no token present | Azul | |
| So far we allow two mechanisms of authentication: * session based * token based If token fails session will be atempted in most cases. So we can't just redirect here or we get a double render error. | |||
| 2013-08-27 | make sure find_record still works with real records | Azul | |
 |
index : leap_web.git | |
| [leap_web] | git repository hosting |
| summaryrefslogtreecommitdiff |