Name |
Last commit
|
Last update |
---|---|---|
.. | ||
accounts | ||
emails | ||
keys | ||
notifications | ||
passwords | ||
preferences | ||
two_factor_auths | ||
_event_table.html.haml | ||
audit_log.html.haml | ||
show.html.haml | ||
update_username.js.haml |
BigW Consortium Gitlab
Previously we were doing all of kinds of code gymnastics and flash abuse in order to work with a Doorkeeper controller but have it _appear_ at the `/profile/applications` path. Fortunately we can just tell Rails to use a different controller to handle that route, and we get the best of both worlds.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
accounts | Loading commit data... | |
emails | Loading commit data... | |
keys | Loading commit data... | |
notifications | Loading commit data... | |
passwords | Loading commit data... | |
preferences | Loading commit data... | |
two_factor_auths | Loading commit data... | |
_event_table.html.haml | Loading commit data... | |
audit_log.html.haml | Loading commit data... | |
show.html.haml | Loading commit data... | |
update_username.js.haml | Loading commit data... |