loomio - helps groups make better decisions together

[girish]

@jimcavoli postgresql has this plugin whitelist, so we have to add citext to it. It's easy to do.

[girish]

@jimcavoli If you update the /home/yellowtent/box/src/infra_version.js to have the latest postgresql container (the hash is in https://git.cloudron.io/cloudron/box/-/commit/23c455043033b4c4a5e7739a1748a2a38c6a9457), then citext should be part of it.

[jimcavoli]

@girish Thanks! trying to figure out where to submit changes for additional extensions - unclear on that from what you've linked, but bumping the infra version got citext out of the way. This time I got smart and checked the rest of them - I believe hstore is already enabled, and plpgsql, so that just leaves pg_stat_statements - which I hadn't brought up previously, but is handy for many reasons, but also required in to get loom up.

Full list of extensions used by loomio:

  enable_extension "citext"
  enable_extension "hstore"
  enable_extension "pg_stat_statements"
  enable_extension "plpgsql"

[girish]

@jimcavoli Thanks, I have added those extensions as well now for the coming release.

[jdaviescoates]

any update on this @jimcavoli ? Thanks!

[jimcavoli]

Still pending; I missed an extension in the earlier ask, but that's been merged, so hopefully this will release shortly after the next Cloudron patch version. It's at the top of my list, so as soon as I can get it working, I'll update here.

[yusf]

@jimcavoli That is good news. Ping if you need testing.

[jimcavoli]

@yusf Will do!

[jdaviescoates]

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

@jimcavoli That is good news. Ping if you need testing.

It's GREAT news!

Thanks @jimcavoli!

[jimcavoli]

I believe this should run on cloudron 6 without issue, but I'm waiting for that update to hit the machine I use to make sure and then we should be able to get this out. The new 2.5 update has some excellent features as well! (which I see no issues with running in this package as soon as it's ready to go)

[marcusquinn]

Very nice, looks like a better alternative to this that I'm seeing used often for Twitter community groups: https://www.mightynetworks.com/

[robi]

This will be useful in at least 2-3 of my many projects.

You can request a specific Cloudron to get the update sooner

[girish]

@jimcavoli If you want to move this along further, that postgresql extension is now enabled in 6.0

[jimcavoli]

@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

[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!