Age | Commit message (Collapse) | Author | |
---|---|---|---|
2014-02-10 | minor: refactor token auth a bit | Azul | |
2014-01-27 | Merge branch 'develop' into feature/messages_api | jessib | |
Conflicts: users/config/locales/en.yml | |||
2014-01-23 | added a customizable 'bye' page for when a user leaves | elijah | |
2014-01-21 | Small optimization to saving message when sending one month warnings. | jessib | |
2014-01-13 | Comment for how to call view that we aren't now using. | jessib | |
2014-01-09 | Some more cleanup, but still want to make sure ↵ | jessib | |
by_user_ids_to_show_and_created_at view is right before issuing pull request. | |||
2014-01-07 | Some refactoring, to simplify user model, optimize, and allow messages to be ↵ | jessib | |
sorted by date (although are not now.) Also, rather than use whenever gem, will have cron job created to call task. | |||
2014-01-07 | Merge branch 'develop' into feature/messages_api | jessib | |
2014-01-07 | only emit pgp keys if they are actually set | Azul | |
if doc.keys has not been set doc.keys[pgp] will raise an error. We always upload the key after signup - but this might fail and there is some time in between. Not checking for this condition lead to errors in the couch logs. | |||
2014-01-07 | remove outdated views that cause errors | Azul | |
The datastructure changes to that email_aliases is not available on the user record anymore. Keeping these views leads to errors on couch servers. | |||
2013-12-31 | Add authentication to API, but not sure it is best way. | jessib | |
2013-12-31 | Removing join-model we are no longer using. | jessib | |
2013-12-31 | Cleanup of code for messages API and cron job for 1 month payment warning. ↵ | jessib | |
Authentication still remaining piece. | |||
2013-12-30 | Fixes to initial go at job to send one month warnings. | jessib | |
2013-12-30 | Merge branch 'feature/messages_api' into feature/messages_cron | jessib | |
2013-12-30 | Change structure to be more no-sql-y, rather than relational. | jessib | |
2013-12-30 | Not actually how we want to do this, but at least finish outlined part, that ↵ | jessib | |
will later be replaced. | |||
2013-12-26 | Very very rough start to having messages for payment automatically created. | jessib | |
2013-12-24 | Catching some corner cases & new tests. | jessib | |
2013-12-24 | Add API tests and some refactoring of messages so we can get a user's ↵ | jessib | |
messages within the webapp. | |||
2013-12-24 | API method to mark a user's message as read (will refactor) | jessib | |
2013-12-24 | Initial start to messages API. | jessib | |
2013-12-23 | Merge remote-tracking branch 'jessib/feature/3389_download_links' into develop | Azul | |
Conflicts: core/app/views/common/_home_page_buttons.html.haml users/app/views/users/show.html.haml | |||
2013-12-22 | locale prefix support: | elijah | |
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path | |||
2013-12-20 | enable billing engine by default, consolidate APP_CONFIG[:payments] and ↵ | elijah | |
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree] | |||
2013-12-19 | Put download link on user page. | jessib | |
2013-12-16 | Fix issue 4756: /login should not crash if one goes there when logged in. | jessib | |
2013-12-16 | Merge pull request #123 from azul/refactor/standartize-user-routes | jessib | |
refactor: remove Overview controller - we can use Users#show | |||
2013-12-13 | refactor: remove Overview controller - we can use Users#show | Azul | |
we were only using Users#show to redirect to the edit action. So I replaced that with the overview and we have no more use for the extra controller. This also simplifies linking to the users in question a lot. | |||
2013-12-13 | make the possible actions for users and admins configurable | Azul | |
with tests | |||
2013-12-13 | refactor: move edit sections into partials | Azul | |
2013-12-09 | Merge pull request #119 from jessib/feature/service_level | azul | |
Feature/service level | |||
2013-12-06 | make sure key responses are plain text | elijah | |
2013-12-06 | simple validation for pgp key format | Azul | |
2013-12-06 | ignore attempts to empty public_key, refactor | Azul | |
refactor: prepare validations of the uploaded pgp keys | |||
2013-12-05 | We won't want service levels in production mode, and have it so this initial ↵ | jessib | |
service level code won't break anything if it isn't set in the config. | |||
2013-12-03 | Some simplification of code. | jessib | |
2013-12-03 | Add ServiceLevel class to wrap config and give accessors. Has some hacky ↵ | jessib | |
parts, but seems like okay generic start for now. | |||
2013-12-02 | Merge branch 'develop' into feature/service_level | jessib | |
2013-11-26 | simple validation for pgp key format | Azul | |
2013-11-26 | ignore attempts to empty public_key, refactor | Azul | |
refactor: prepare validations of the uploaded pgp keys | |||
2013-11-25 | Give 404 error if one goes to /key/user for non-existing user. | jessib | |
2013-11-21 | Refactoring of code, and tests. | jessib | |
2013-11-18 | Need to cleanup some, but start to show public key for /key/username | jessib | |
2013-11-18 | Start of service level code, which will be tweaked | jessib | |
* stores desired & effective service level * whenever desired level is changed, effective level will be updated * allows user to set their desired service level * allow admin to update desired & effective service level | |||
2013-11-12 | Merge pull request #110 from azul/feature/cleanup-expired-tokens | jessib | |
Feature/cleanup expired tokens | |||
2013-11-08 | fix cornercase of non expiring tokens | Azul | |
2013-11-08 | Token.destroy_all_expired to cleanup expired tokens (#4411) | Azul | |
2013-11-06 | use the account lifecycle from UsersController#destroy | Azul | |
2013-11-06 | destroy all tickets created by a user when account is destroyed | Azul | |
In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed. The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id. I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine. |