Migrate ln_login out of encrypted column to ln_account, so we can look up users by login
Add Webhooks controller and config for allowed IPs
Add send_message API to ejabberd service, plus respective background job
Add Webhook for incoming sats, which notifies the user via XMPP message
* Migrate `ln_login` out of encrypted column to `ln_account`, so we can look up users by login
* Add Webhooks controller and config for allowed IPs
* Add `send_message` API to ejabberd service, plus respective background job
* Add Webhook for incoming sats, which notifies the user via XMPP message
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ln_loginout of encrypted column toln_account, so we can look up users by loginsend_messageAPI to ejabberd service, plus respective background jobthat's super cool!
from checking the code it looks good to me.
I have a few minor comments
@@ -0,0 +5,4 @@def lndhubbeginpayload = JSON.parse(request.body.read, symbolize_names: true)doesn't rails automatically parse the JSON because the proper content type is set?
so
params[:type]andparams[:user_login]should be enough?I didn't know, so I tried (also with explicitly setting the content type in the spec). Doesn't do it.
@@ -0,0 +11,4 @@head :unprocessable_entity and returnenduser = User.find_by(ln_account: payload[:user_login])should not be the case, but this might be nil. maybe we should do a
User.find_by!Good idea! Fails much cleaner and more expressively than when trying to access properties on
nillater.