loomio - helps groups make better decisions together
-
@jimcavoli If you want to move this along further, that postgresql extension is now enabled in 6.0
-
@girish Yeah, I've picked it back up and all the basics are looking good. I've got it booting up completely on my dev box. Trying to work out the websockets piece now, which is pretty important. Just banging head against nginx for the most part
-
Yeah, nginx/websocket requires this magic incantation - http://nginx.org/en/docs/http/websocket.html (if that is what is blocking you)
-
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.
-
-
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
recvmailwith 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_TOwhile leveraging the+-delimited subaddresses feature would be similar to https://github.com/loomio/loomio/compare/master...piratas-ar:pipe_to_api but withapp/helpers/email_helper.rbusing 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! -
@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
sendmailandrecvmailare 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.1User doesn't exist: loomio.app@example.comwhen emailing either the nakedloomio.app@example.comaddress or a subaccount address (ultimately the one I care about for reply-by-email) likeloomio.app+subaccount@example.comAction: 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.comOtherwise, 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!
-
@jimcavoli Where is the repo for this? I am not finding it in https://git.cloudron.io/jimcavoli
-
-
@jimcavoli Thanks! Will take a look.
-
Just giving this another little bump
@girish did you ever manage to have a look at @jimcavoli's package?
-
@bubonicfred @girish any progress on Loomio? Just trialling it in our organisation and inclusion would make the case for Cloudron stronger for us.
-
Friends made a startup in this decision management field called KIE Labs - https://www.kielabs.com
-
@jdaviescoates @girish
Just bumping this again,
possibly willing to help test -
-
