Cloudron Forum

Nice. +1

The project currently does not use git tags properly and the changelog is more like a diff of commits between specific git sha1s...

The input field value is correct. However it is only indicating the starting point of the port range here: 40000 -> 40100

We have added that feature specifically for the SFU use-case so the UI was kept unchanged to not confuse every other app, where its only about 1 port.

@avatar1024 depends. Have to investigate how compatible the integration is with say something like keycloak.

I use groups a lot and this sounds like a very useful feature to have.

I can confirm that with 1.4.18 authentication now works as expected! Thank you @MiroTalk and @staff !

Thank you, works perfectly!! You guys are super heros. And thank to @vladimir-d for the fix on that particular issue! (though I couldn't see it in the release notes of the package)

One issue I had is that the instance was looking all broken after the package update, I had to delete website cookies and data for it to work (might have to do with all the CSS changes in the release).

@avatar1024 ah, I missed that part that you restored! Thanks for reporting.

@avatar1024 Might be best to ask this upstream at https://github.com/docusealco/docuseal/discussions

For the first question: maybe https://github.com/docusealco/docuseal/issues/132 ?

Well spotted, I had done a search in there before posting but missed it. Thank you!

And well, obviously that's a shame.

Many thanks for this. The function is not actually activated but for some reasons the client seem to apply some kind of spam filter (even though when I open my spam folder it explicitly says that spam filtering is not done by the client but by the server). Anyway I definitely know where to look now so THANK YOU for your help and sorry for the tangent as this is not a Cloudron issue

Turns out the mountpoint for backups, which is /mnt/cloudronbackup/ had leftover files, which prevented it from being mounted. After clearing that folder it works fine.

I will see how we can better communicate this into the dashboard to make this more obvious in the future.

Great tip, thanks!

Agree it's insane the default is only once a week. Perhaps we should report this upstream...

@girish said in Mailing list feature: basic moderation:

I also feel this workflow is very specific to your request. Usually, people want real lists and moderators don't want to manually forward emails. Just my 2c.

Perhaps it is specific to my workflow and I'm sure people would prefer real lists 😊...but I would imagine people would still prefer a basic / manual kind of moderation rather than none at all. Currently we have the option of either a list in which anyone can send to (including spammers), or a fully private list unreachable from external people. So I was looking for a technically simple way to achieve an in-between, even if basic and unperfect, for lack of a better solution likely to be available on Cloudron anytime soon (in a similar way when I proposed to implement private list, which it turned out was simple enough and so you - as always brilliantly - implemented the idea). But I get that in this case it's not so simple 🙂

Thank you for looking into it anyway and for providing feedback.

@girish said in Mailing feature: add users and groups as members:

When added to a list, are you expecting the primary email of the user to be used ?

Indeed 🙂

I have clarified the text a bit more now.

@avatar1024 thanks we will update. The reason for it not being updated yet, is that their package repositories are usually lacking behind their release tag by a day and we have to wait for those.

It just so happens, that the whole file is now renamed in upstream since their loolwsd part is now called coolwsd 🙂

The package should do the config file rename and sed things for that renaming automatically.

I pushed our fork for now.