I think we're on track to making deployd actually useful, more so than just looking like a cool idea and giving up on it after running into so many issues
I almost did, the fact you couldn't intercept login was the biggest problem for me. I don't see how any public facing real app can not be interested in that event. There was no bruteforce protection possible otherwise.
We should probably make that default in a subsequent release.
there's still too much disclosure than I would like
so it should be something for the roadmap
In my app, I extend the User Collection and override the functions, in order to get what I want.
sure but that implies some knowledge of deployd innards that some new guy trying it out won't have
we should have the basic functionality readily possible in the core
which with the login stuff is probably mostly done now, there are still some things bugging me, like the lack of require() being available by default
it's also something extremely likely someone will need
but I have that fixed with a custom dpd extension
@NicolasRitouet hey, there are lots of "Issues" on github that should be closed because they're more or less resolved. I'm looking through issues to see if there's any other bugs that could potentially be important. When you can, the issue list should be cleaned up.
@NicolasRitouet@ericfong , I just implemented promises into the internal client aka deployd/deployd#375
it can wait for 0.9 if you want although all tests pass and I made a test for it as well