summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-12-02Merge pull request #118 from azul/feature/validate-pgp-keysjessib
Feature/validate pgp keys
2013-12-02Version 0.2.8 - release candidate0.2.8.rcAzul
* Return public key on /key/:login * rake tasks clean up expired tokens and sessions (#4568) * rake task to dump design docs to files * add dump_design_docs to CouchRest::Model::Utils:Migrate * rename ticket title to subject
2013-11-29Merge remote-tracking branch 'origin/master' into developAzul
2013-11-27minor: rename test to what it actually testsAzul
[skip ci]
2013-11-26simple validation for pgp key formatAzul
2013-11-26ignore attempts to empty public_key, refactorAzul
refactor: prepare validations of the uploaded pgp keys
2013-11-25Merge pull request #117 from jessib/feature/return_public_keyazul
Feature/return public key
2013-11-25Give 404 error if one goes to /key/user for non-existing user.jessib
2013-11-21Refactoring of code, and tests.jessib
2013-11-21Merge branch 'develop' into feature/return_public_keyjessib
2013-11-21Merge pull request #116 from azul/feature/rake-tasks-for-cleanupjessib
rake tasks for cleanup
2013-11-21Merge pull request #115 from azul/feature/dump-design-docsjessib
Enable dumping design docs to files
2013-11-21rake tasks clean up expired tokens and sessions (#4568)Azul
2013-11-19couchrest:dump task will dump all design docsAzul
2013-11-19add dump_design_docs to CouchRest::Model::Utils:MigrateAzul
This is similar to the migrations but instead of uploading the design documents to couch it stores them in tmp/database/design.json within the rails directory. database is the supposed database name without prefixes or suffixes design is the name of the design doc CouchRest model would have created The files also contain a couchrest checksum so couchrest can detect they are up to date. This commit also cleans up a few redundant things in the extension to CouchRest::Model:Utils::Migrate that we used to have. There's no need to loop through the 'normal' models in load_all_models_with_engines since load_all_models_without_engines already does that. We were also overwriting all_models_and_proxies with exactly the same code as in the original.
2013-11-18Need to cleanup some, but start to show public key for /key/usernamejessib
2013-11-18Merge branch 'develop' - hotfix for database changeAzul
2013-11-18Merge pull request #114 from jessib/feature/rename_ticket_title_to_subjectazul
Feature/rename ticket title to subject
2013-11-18Remove unnecessary label.jessib
2013-11-18Merge branch 'develop' into feature/rename_ticket_title_to_subjectjessib
2013-11-15Version 0.2.70.2.7Azul
* ensure that we only copy files for customization when restarting the app (#1300) not every time a rake task is run (especially since some rake tasks get run as root!) * improvements to the download button (proper localization, better image, better hooks for customization) * added support for easier customizations via "config/customization" directory (#1300) * log json request errors and their backtraces * show Ticket with the appropriate error messages. (*4453) * update readme to require ruby 1.9.3 instead of 1.8 * Token.destroy_all_expired to cleanup expired tokens (#4411) * use the account lifecycle from UsersController#destroy (#4216) * destroy all tickets created by a user when account is destroyed (#4216) * integration test for blocking handles after account destroyed (#4216) * disable identities to block handles after a user was deleted (#4216) * notify user their account was successfully deleted (#4216) * Fix button to enable account (#4246)
2013-11-15Merge branch 'develop'Azul
2013-11-15Merge pull request #113 from elijh/feature/customizeazul
Feature/customize
2013-11-15fix problem with custom scss files and precompiling assets in production mode.elijah
2013-11-14ensure that we only copy files when running restarting the app, not every ↵elijah
time a rake task is run (especially since some rake tasks get run as root!)
2013-11-14minor improvements to the download button (proper localization, better ↵elijah
image, better hooks for customization)
2013-11-14added support for easier customizations via "config/customization" directoryelijah
2013-11-12Merge pull request #112 from azul/debug/log_json_errorsjessib
make sure we log json request errors and their backtraces
2013-11-12Merge pull request #110 from azul/feature/cleanup-expired-tokensjessib
Feature/cleanup expired tokens
2013-11-12make sure we log json request errors and their backtracesAzul
2013-11-12Merge pull request #111 from jessib/bugfix/4453_missing_templateazul
Maybe not ideal fix, but since there is no edit view, we want to show th...
2013-11-11Rename ticket title to be subject, as that is what we are displaying it as.jessib
2013-11-11Maybe not ideal fix, but since there is no edit view, we want to show the ↵jessib
show view with the appropriate error messages.
2013-11-11Merge pull request #109 from azul/feature/clear-all-data-of-deleted-userjessib
Feature/clear data of deleted user
2013-11-10update readme to require ruby 1.9.3 instead of 1.8Azul
2013-11-08removed outdated test.Azul
2013-11-08fix cornercase of non expiring tokensAzul
2013-11-08Token.destroy_all_expired to cleanup expired tokens (#4411)Azul
2013-11-07only check number of disabled identities to make test more robustAzul
2013-11-06use the account lifecycle from UsersController#destroyAzul
2013-11-06destroy all tickets created by a user when account is destroyedAzul
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.
2013-11-06Ticket.destroy_all_from(user) - remove all tickets created by a userAzul
We'll use this to clean up after user destruction
2013-11-06refactor: split up and cleaned up ticket validation testsAzul
2013-11-06integration test for blocking handles after account destroyedAzul
has not been run yet.
2013-11-06refactor: extract method on account testAzul
also test one can't login anymore after destroying the account.
2013-11-05Identity.destroy_all_disabled will clean up disabled identitiesAzul
This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.
2013-11-05disabled identities to block handles after a user was deletedAzul
2013-11-05refactor: Identity.disable_all_for(user) on user destructionAzul
This way the identity model defines how identities should be disabled. We currently still destroy them. But it will be easy and nicely isolated to change this next.
2013-11-04Merge pull request #108 from azul/feature/proper-user-deletionjessib
notify user their account was successfully deleted (refs #4216)
2013-11-04Version 0.2.60.2.6Azul
* reset button state from 'loading...' after failed login attempt (#4231) * use https sources in Gemfiles and documentation(#4109) * include Gemfile.lock to prevent unintended updates (#4174) * fixed download urls to get latest versions for mac, android and windows * test api login with umlauts in password