We still have to wait until https://github.com/nextcloud/server/issues/11670 is resolved unfortunately.

Cloudron will "take over" the server and also manages the packages and services, which are installed. Generally it is not supported to install anything on the side. In this case Cloudron depends on mysql-server-5.7 which will probably uninstall mariadb through apt.

Nice news ! :D

@nebulon Yes I know but I think it's a kind of "dirty intregation" regarding how much you have implemented Amazon/DigitalOcean S3 ... And I'm probably not the only one that need a backup in French Infrastructures. :) @girish Hum, So bad because it's totally functionnal for me ... :( I don't know if there is some limitations for others countries.

If this is a OpenVZ VPS you're trying to set up, this might not be possible. As stated here: Cloudron does not support running on ARM, LXC or OpenVZ.

@necrevistonnezr Still evaluating what is the best option to update existing installations. Most likely we won't do dist-upgrade automatically. Also, new installations will default to 18.04.

@nebulon Thank you very much. Yes, the server was done for a while but now back online :).

I would love to see Bookstack on Cloudron. Instant install.

@girish Thanks ;)

Hi @nebulon , I made a few tests today since I remembered that there is a dockerImage value in CloudronManifest.json, but I am not quite sure how to use it. My current experiment is at https://github.com/fbartels/bitwarden_rs/tree/cloudron/cloudron. It uses a new Dockerfile that uses the multi stage Dockerfile as a base and uses a Cloudron Base Image for the last stage. But it seems he does not take my dockerImage. The only way he pulls in my image is by calling cloudron install --image fbartels/bitwarden-cloudron from the commandline. For everyone else reading this. This is up until now only a build, the app is still missing all integration pieces and won't work withing Cloudron (yet).

Please note that existing Cloudrons will not use wildcard certs automatically. You have to go to domains -> edit the domain -> advanced -> Choose wildcard provider. New apps will then start using a wildcard cert automatically. Existing apps will start using wildcard certs once the existing ones expire. If you are impatient, you can just click on 'configure' of an existing app and click save to get a wildcard cert. Also, wildcard certs only work with programmable DNS. Finally, for new Cloudrons, wildcard is the default.

Currently there is no integration between Cloudron groups and groups inside an app. I agree that this is a good feature to have though.

Cloudron 3.2 is now available for all. We pushed a mail container update as part of 3.2.2. This contains an important bug fix where the mail server keeps getting locked up.

Maybe https://pleroma.social/ could be an alternative to Mastodon From https://blog.soykaf.com/post/what-is-pleroma/: Pleroma is a microblogging server software that can federate (= exchange messages with) other servers that support the same federation standards (OStatus and ActivityPub). What that means is that you can host a server for yourself or your friends and stay in control of your online identity, but still exchange messages with people on larger servers. Pleroma will federate with all servers that implement either OStatus or ActivityPub, like GNU Social, Friendica, Hubzilla and Mastodon. How is it different from Mastodon? If you are currently using Mastodon, you are probably interested in the differences between Mastodon and Pleroma. Here are some of the big ones. Lower system requirements. {...} Less moving parts. {...} Internally ActivityPub. {...} Compatible with Mastodon clients (including the Mastodon frontend).

@nebulon ok thanks for the info, appreciate it.

This seems awesome, still reading about it.