loomio - helps groups make better decisions together
-
@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
-
@jimcavoli ask away, nginx is pretty straight fwd.
-
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
-
@girish Thanks for fixing that up - packaging to date is at https://git.cloudron.io/jimcavoli/loomio-app
-
@jimcavoli Thanks! Will take a look.
-
@girish How's this going?
-
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.
-
I've yet another org interested in this.
-
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 -
do we do bounties on apps? I'd put one on this
-
@ianhyzy you could reach out to @atridad he did a great job of packaging Humhub for me.
-
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?
-
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?
-
@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.
-
@girish On it; hopefully will have that today
-
@girish Opened it up and got to updating - was reminded that the issue was the inbound email side of things, not the Dockerfile on this one...it's the OpenSlides packaging stalled on the multistage builds (which needs some more revision and I'll update soon). In any case, I've updated it to use
cloudron/base:3.0.0and Loomio at2.8.3(latest) locally and on my test box. The outstanding issue with inbound mail remains, plus a new, if minor, issue with RedisAUTHfor the channel server - any chance we'll see Redis updated to 6.x soon?I can work on alternatives to make the channel server Redis connection happy, but I still need help on the inbound email side of things. Sending seems fine, but replies (the inbound-to-app side) bounce immediately. I've pushed the changes for the newer versions to https://git.cloudron.io/jimcavoli/loomio-app and included the caveat(s) about the broken components in the commit message for now.
-
@jimcavoli thanks! We can follow up on the recvmail issue in the other thread. As for redis, is the issue that it cannot work with redis 5 at all? There is a flag in redis addon to disable auth entirely, would that help?
-
here - https://docs.cloudron.io/packaging/addons/#redis . The
noPasswordflag in manifest. -
@girish Yeah, I tried setting that, but the issue is that one part of the app is sending the two-argument version every time, which 5 and lower just don't know how to handle
-
@jimcavoli I see. What's interesting is that https://help.loomio.org/en/dev_manual/setup_dev_environment/ just suggests installing redis via apt but redis 6 is not yet in ubuntu (only via a ppa). Another idea is to maybe use the previous release of loomio and then we can move it once we have redis 6 available. Is that an option?
-
@girish yeah, I don't see why not. It works in an older version. I may be able to pin back the specific dependency as well (it's the node dependency from https://github.com/loomio/loomio_channel_server that seems to be doing it). I'll play around with it a bit while we work on the
recvmailthing in the mean time. -
@jimcavoli I have opened https://git.cloudron.io/cloudron/box/-/issues/804 to track for next release
-
Got 7.0.1 loaded up on my testbed machine...going to re-update the packaging as needed and ensure
recvmailis integrated properly, then we should be good to go here. Hoping for O(days) on that, may be O(weeks) given schedules the next few weeks. -
@jimcavoli awesome, let me know if
recvmailworks or not -
@jdaviescoates said in Cobudget - A collaborative funding tool for crowds with purpose.:
BTW, the backstory to Cobudget is a must read imho
Same goes for Loomio actually
-
@jimcavoli @girish Any update on this?
-
@girish Is it possible to test this somehow?
We're using it in our org and would like to let the team know when we could include it with our Keycloak/Cloudron services.
-
@Sam_uk Not sure what the current status of the package is. @jimcavoli do you know?
