| Age | Commit message (Collapse) | Author |
|---|
|
[skip ci]
|
|
|
|
refactor: prepare validations of the uploaded pgp keys
|
|
* 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
|
|
* 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
|
|
|
|
Feature/return public key
|
|
|
|
|
|
|
|
rake tasks for cleanup
|
|
Enable dumping design docs to files
|
|
|
|
|
|
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.
|
|
|
|
|
|
Feature/rename ticket title to subject
|
|
|
|
|
|
* 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)
|
|
|
|
Feature/customize
|
|
|
|
time a rake task is run (especially since some rake tasks get run as root!)
|
|
image, better hooks for customization)
|
|
|
|
make sure we log json request errors and their backtraces
|
|
Feature/cleanup expired tokens
|
|
|
|
Maybe not ideal fix, but since there is no edit view, we want to show th...
|
|
|
|
show view with the appropriate error messages.
|
|
Feature/clear data of deleted user
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
We'll use this to clean up after user destruction
|
|
|
|
has not been run yet.
|
|
also test one can't login anymore after destroying the account.
|
|
This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.
|
|
|
|
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.
|
|
notify user their account was successfully deleted (refs #4216)
|
|
* 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
|
