Topics created by fbartels

@humptydumpty to reliably update i ended up always updating the docker tag to the desired version. With the tag updated you just need to run flyctl deploy again.

Hi @girish, ah that fully explains why I cannot interact with the processes running in the container. While your design idea is probably suitable for most cases it won't really work for this specific one.

But no harm done, then I will just add a cron service to my app container directly.

@fbartels said in Duplicate entry '172.18.17.187' for key 'apps.containerIp':

PS: the synapse documentation states that the well known settings are under advanced in the domain settings

Fixed!

@jdaviescoates said in Element based video meetings:

It says they plan to add an SFU

Where did you read this? The project says "Showcase for full mesh video chat powered by Matrix, implementing MSC3401."

edit: nevermind, it's in the blog post

OK, so the issue was that the app thinks it's configured for LDAP, but it's not (since it's a public facing instance, we disabled LDAP). I have removed the LDAP panel entirely from the login page. Thanks for reporting @fbartels

This should be fixed with the next release. There were a couple of state issues which needed fixing.

more likely a browser hiccup..

@doodlemania2 I was looking for some further information on this.

Paperless-ng uses Tika (to extract data from other file types) and Gotenberg (for pdf conversion) for this.

More at https://paperless-ng.readthedocs.io/en/latest/configuration.html#tika-settings

@fbartels I can vouch for Siteground, they have a stellar customer support and very good service.

Would it be not for Cloudron, my WordPress websites would still be with them.

Small update. The long wait time when logging in seems to be related to LDAP users. At least when logging in with a user that has been created manually the login immediately succeeds.

But this seems unrelated to the long wait time for the request when submitting the shopping cart, as this also happens when the ldap plugin is deactivated.

thanks, I have made a new package now.

@nebulon thanks. works like a charm now.

@girish Thanks for looking at this. Just triggered another backup with all apps active and it succeeded. I guess then it's finally time to move to the new hardware (plus making sure that the new system is using the c locale by default)

How much of this will change with Multi-Cloudron?

@robi
I meant Linux kernel Wireguard.

how embarrassing. You're absolutely right. I was searching after ghosts.

@fbartels awesome, thanks for testing. I am fixing the graphite issue, that error is something else. Fixed in https://git.cloudron.io/cloudron/box/-/commit/f7bd47888ac157fc5b86021f6458b6a7f0d3fba8

Right, since you have the access token in this case in a new tab simply in the local storage, the session is refreshed and you see the files. I will fixup the login state/login button to show somethign like "Admin Dashboard" or so.

hm.. I can also not reproduce it. Yes, that login url I did get as well, but when then forwarded to the logged in view (the one with index.php?r=admin) it did fail before.

I have added cloudron update --appstore-id {id} for the next release.

@nebulon thanks! Indeed the upload now succeeds with the new version. For the wrong timestamp i'll just touch the folder once before calling surfer. Maybe it eventually gets fixed in hugo itself.

cc @plusone-nick . He knows all sorts of no-code apps.

@marcusquinn generally yes, you could stream a webinar in such a way (have done this in the past with youtube). The thing you have to be aware of is that there is a delay involved (incoming buffer on the platform and then another buffer at the client). So it's not really suited if you want to react on realtime feedback/questions.

@marcusquinn see my post about n8n at https://forum.cloudron.io/topic/1939/n8n-io-zappier-ifttt-integromat-alternative/13?_=1605126531115 - short version is that it's been packaged, it's just not primetime-ready

Thanks for that, I've release a new package version with it.

The new package version now disables that pid-file so hopefully this issue will be gone.

Both issues are addressed with the new version 0.3.0 now

@aizat This would be better posted in the App Request section.