Topics created by fbartels

@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)

I don't have a script but if you want to keep the downtime low, we added this dry run feature last release - https://docs.cloudron.io/backups/#dry-run . This way you don't need to shutdown the old server while things are restoring on the new server. Of course, you have to be careful not to add new data in the old server since it won't be part of the backup but atleast the site will be up.

@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.

great! luckily we can re-watch 😄

Agola is really quite nice.

The following configuration needs to be added to the identifier registration of Kopano Konnect to enable SSO with Rocketchat:

- id: rocketchat.9wd.eu name: Rocketchat trusted: true application_type: web redirect_uris: - https://rocketchat.9wd.eu/_oauth/konnect

Remember to restart Konnect after modifying the registry. If you want to verify that the configuration was properly loaded you have to modify log_level in /app/data/konnectd.cfg to read /app/data/konnectd.cfg. With another restart Konnect will then print a message like the following at startup:

Apr 20 20:21:30 time="2020-04-20T18:21:30Z" level=debug msg="registered client" application_type=web client_id=rocketchat.9wd.eu insecure=false origins="[https://rocketchat.9wd.eu]" redirect_uris="[https://rocketchat.9wd.eu/_oauth/konnect]" trusted=true with_client_secret=false

In Rocket.chat the following configuration needs to be added. For this go into the admin backend, select "OAuth" and there "Add custom oauth". I am using the following settings:

URL: https://meet.9wd.eu Token Path: /konnect/v1/token Token Sent Via: Header Identity Token Sent Via: Same as "Token Sent Via" Identity Path: /konnect/v1/userinfo Authorize Path: /signin/v1/identifier/_/authorize Scope: openid profile email Id: rocketchat.9wd.eu Secret: rocketchat Login Style: Default Button Text: Kopano Konnect (needs to be something the user can relate to) Button Text Color: #FFFFFF Button Color: #13679A Username field: preferred_username Merge users: false

After storing these log out of Rocket.chat and you will see a new button on your login page titled "Kopano Konnect", which will then use the new login method.

Good point, I thought this would be triggered by the security update job from ubuntu already, but apparently not.

Nice, thanks @girish

I have created https://git.cloudron.io/cloudron/box/issues/649

Thanks for the heads up and the workaround!

The last update explicitly removed the admin status propagation from Cloudron user accounts to the app. This is done to unify how user accounts get permissions assigned within all apps. The idea is, that the Cloudron admin status is not carried over to apps, since apps have too many different concepts what an admin is and is not.

I guess there is no good way without requiring manual permission changes to move to this new understanding what admin means on Cloudron.