loomio - helps groups make better decisions together

[robi]

@jimcavoli ask away, nginx is pretty straight fwd.

[girish]

Yeah, nginx/websocket requires this magic incantation - http://nginx.org/en/docs/http/websocket.html (if that is what is blocking you)

[jimcavoli]

I had a breakthrough with the dumb websockets issue. Hooray! This one should be ready shortly. I know it's been highly requested and hotly anticipated (for me as well) so it's my top packaging to finish. At this point, after a few other tweaks, I'm fairly sure I've got this working. I'll do some final testing tonight, but I expect that I should have an initial build together by this weekend.

[marcusquinn]

@jimcavoli

[jimcavoli]

It does appear that nearly all features are working in my test build. There is one last challenge remaining here - a potentially notable one. Inbound email for loomio is, in its usual deployment form, handled by a custom sub domain with an MX pointing to a nodejs mailin server to convert messages to webhooks. My plan for the cloudron packaging is to use the recvmail with a custom poller process that will grab emails and POST them as required to the app.

However, this will require a patch to the underlying software as well. The patch to make loomio use the configured CLOUDRON_MAIL_TO while leveraging the +-delimited subaddresses feature would be similar to https://github.com/loomio/loomio/compare/master...piratas-ar:pipe_to_api but with app/helpers/email_helper.rb using the ENV var rather than the hard-coded "loomio" shown in the linked patch. It's a pretty minimal change to get the packaging working so that all the various loomio services operate out of the singular cloudron container, so I'm comfortable pressing ahead with that approach, but if anyone can think of a better solution, please let me know!

[jimcavoli]

@girish or @nebulon Maybe you can help here? I've got everything in place as far as I can figure for email. Outbound works fine, but I keep getting bounces when attempting to reply. Both sendmail and recvmail are enabled for the app (in that order in the manifest), but something doesn't seem to be working nicely on the Cloudron side. I've confirmed that I get a 550 5.1.1 User doesn't exist: loomio.app@example.com when emailing either the naked loomio.app@example.com address or a subaccount address (ultimately the one I care about for reply-by-email) like loomio.app+subaccount@example.com

Action: failed
Status: 5.1.1
Remote-MTA: 127.0.0.1
Diagnostic-Code: smtp;550 5.1.1 <loomio.app@example.com> User doesn't exist: loomio.app@example.com

Otherwise, as far as I can tell, I think everything is functioning correctly, but the reply-by-email and custom poller I've written can't be exercised and fully verified until I can sort out this mail delivery issue. Very excited to finally be (nearly) done with this one!

[girish]

@jimcavoli Where is the repo for this? I am not finding it in https://git.cloudron.io/jimcavoli

[jimcavoli]

@girish Thanks for fixing that up - packaging to date is at https://git.cloudron.io/jimcavoli/loomio-app

[girish]

@jimcavoli Thanks! Will take a look.

[bubonicfred]

@girish How's this going?

[jdaviescoates]

Just giving this another little bump

@girish did you ever manage to have a look at @jimcavoli's package?

[Sam_uk]

@bubonicfred @girish any progress on Loomio? Just trialling it in our organisation and inclusion would make the case for Cloudron stronger for us.

[yusf]

I've yet another org interested in this.

[robi]

Friends made a startup in this decision management field called KIE Labs - https://www.kielabs.com

[bubonicfred]

@jdaviescoates @girish
Just bumping this again,
possibly willing to help test

[ianhyzy]

do we do bounties on apps? I'd put one on this

[Sam_uk]

@ianhyzy you could reach out to @atridad he did a great job of packaging Humhub for me.

[jdaviescoates]

Off topic:

@sam_uk said in loomio - helps groups make better decisions together:

@atridad he did a great job of packaging Humhub for me.

I'm assuming/ hoping the plan is to get Humhub into the Cloudron App Store too, right?

[jimcavoli]

I can take a look at making sure the packaging code is up to date, but it's very much working on a test instance still. Only issue was @girish building / testing - happy to work on that part of it if needed...I could make it a straight-through Dockerfile rather than BuildKit dependent - though it'll take a fairly long time to build that way, maybe that's just what we need to do?

[girish]

@jimcavoli ah nice, if you can update the base image to 3.0.0, then I can take a look into publishing it. In fact, I am not sure why I didn't look into this further. Would be great to make it a straight through Dockerfile as that's how all the other packages are.