Not sure if that's the right category, but here goes.
I want to implement a plugin which makes it so the email addresses of registered users are stored hashed for privacy reasons.
I think I can use action:user.email.confirmed to overwrite the email with its hashed version.
I want to still support password reset and to that end I want to use the hashed provided email to get the uid of the user.
Would it be possible to add a hook for filtering the email provided to getUidByEmail here?
Additionally, in order to use the non-hashed email as the address, it would also require passing the user provided email in params here.
Yeah, I just took a look at my ~, I have the gits for nodejs 0.10.35, redis 2.8.19, and nodebb 0.6.0 that I built from source. These are not the legacy versions suggested on the docs, but they are the ones I got working on my Debian Wheezy. (I built them with the instructions from their gits, not the nodebb docs)
I just noticed there was a sections about using a dot-deb for install, I don't remember if I tried it that way, but it might be easier if it works.
I hope this helps in some way, I'm a bit of a newb myself. 😉
Of course, we do have docs so you should try it yourself just back up everything first!
Edit: to answer your original question, we do plan on building an upgrade button into our hosting plans control panel - right now we just upgrade customers manually. It's probably impossible (or hard) to make an app upgrade itself via acp, we would need to make the acp a standalone application (we've toyed around the idea, but not worth the development time)