I've got a branch where I've almost gotten LDAP syncing fully working, but invites don't seem to be working properly. Even if I try to send an invite directly through the web interface, it just hangs. The user shows in the list, however the logs never show a success or failure response for the request. I've checked the SMTP settings and they appear to be correct. I'll keep debugging though. https://git.cloudron.io/iamthefij/bitwardenrs-app/tree/ldap-sync

Thanks for working on it! Maybe @girish can help with the nginx config or at least confirm if changes are possible to accommodate Authelia.

@fbartels Indeed! I changed the title accordingly.

@nebulon Thank you. I have done that but I am still running it issues. I have set over 2GBs to the app in the advanced tab but it appears that PHP is still limited to 128MB. I need a way to up that memory... Typically, I would do that in the .htaccess file but it appears those are read-only on Cloudron...? How else can I up the PHP memory limit? php_value memory_limit 2048M

Hi there, in such a case, on Cloudron you would setup a redirection instead https://cloudron.io/documentation/apps/#setting-up-redirections This will allow the app (in this case wordpress) to operate on a single specific domain (either www.example.com or example.com) while being reachable from both.

As I have no knowledge of this technology, asking for help is my only option at the moment. Could this FAQ entry from the OpenVPN website be of help to identify the reason for my SSL protocol errors, and how to solve it? http://ics-openvpn.blinkt.de/FAQ.html

So since matrix.org’s development infrastructure got megaowned today i figured I’d put this here: After Matrix has restored its major services, they noticed that the GPG keys used for signing packages where compromised. The key IDs are: AD0592FE47F0DF61 (synapse) E019645248E8F4A1 (Riot/Web) Please make sure to no longer use those keys.

@ruihildt Thanks Then I will cross my fingers, that it's coming soon.

Thinking about it, if there were going to be a bigger, badder SSO solution "baked in" to the platform, keycloak (https://www.keycloak.org) may be the better tool to close some of that gap than Shibboleth for the job (OpenID Connect, OAuth 2.0, and SAML support built-in; similar flexibility on the backend). My main thought in the use case of SSO apps is that SSO as a platform component is, to date, a platform-internal feature, and I think there's a huge benefit to being able to essentially treat Cloudron as your authoritative directory / user store and leverage it for SSO with SaaS and other strictly off-host products.

Another option is to simply Disable mail and then Enable mail for the domain. This will effectively end up copying the certs.

@ebelinski said in What does it take to run and manage Cloudron in the longterm?: Hi everyone, I am a bit of a novice when it comes to devops. I am evaluating Cloudron right now, which I installed as a DigitalOcean droplet. I then installed Nextcloud and Collabora using the instructions. So far, everything has been amazingly smooth. I didn't even have to SSH into my droplet and I haven't run into any difficult setup issues. But I know that all VPSes at some point require maintenance. There will always be updates to apply and issues to fix. So my question is, if I keep using Cloudron for the months and years to come, what am I getting myself into? Is this whole system more or less a turnkey solution that updates itself and won't exhibit any problems, or will real devops skills be required? If I had off the management of a Cloudron VPS to someone else without devops experience, will they have difficulties? Thank you. Cloudron is incredibly stable. I have minimal devops skills and I've been running it for 1.5 years. Most issues I had was because of my choice of a dirty cheap VPS and the support is really good. If you keep external backups, even reinstalling/moving server is straightforward by following instructions. The most difficult part is the install, so once it's running, as long as you're not out of resources, you can definitely explain how to use/install apps to someone without devops skills.

@murgero said in Cloudron 3.6 - new plans: @girish Why not have them use LAMP, which is what this was made for? Leave the current Wordpress as is, and not make another one. No one is stopping them from using common sense and installing Wordpress in the COMPLETELY OPEN LAMP Stack app.. The promise of Cloudron is to have one-click install app. It's a better version of Plesk+Softaculous. In this regard -and with Wordpress is the most popular app on Cloudron- having a Wordpress unmanaged app is good to have. Cloudron could attract a lot of users from these platforms and make life easier to a lot of webdevs/users. in terms of Cloudron experience, I think it would be good to only have one "Wordpress" in the appstore, and have then the managed/unmanaged choice coming up at install time. (which would create actually 3 choices, managed LDAP / Managed non-LDAP/ Unmanaged) As for SFTP support, I'm looking forward to it.

Also, this app is actively in use in a few universities. If you want to deploy this app for students with integration with your universities' user directory, please contact support@cloudron.io

This is now available in the appstore - https://cloudron.io/store/org.jupyter.cloudronapp.html

This is done by now! We are currently even testing the new Bedrock (previously pocket) version.

Thanks for the heads up, i posted a reply now with more details on why we have that base image and how our update strategy is.

The Unmark development seems to be up again. https://github.com/cdevroe/unmark/commits/master