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

@mgn841 No, but it means it should be easier to package it to Cloudron.

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

"Code-server is VS Code running on a remote server, accessible through the browser."

https://github.com/codercom/code-server

Try it out

docker run -p 127.0.0.1:8443:8443 -v "${PWD}:/root/project" codercom/code-server code-server --allow-http --no-auth

First of all, domain level separation would be really great. (it makes sense, because there already email which are also domain related)

Then we could maybe have "favorite" apps, appearing on top.

Renaming app would be useful, if this could be taken into account also in the notifications: sometimes we have the docker ID of the app, but it isn't always really helpful when there's no context added.

Related to the same page, it would be helpful to have a different tile color for apps which are crashed or in a bad state. Right now if I see an app with ID has crashed alert, I have to scroll through all my apps to find the correct one.

@girish do I have to update my wordpress, or is it a platform change?

If it benefits the perfomance, I think that would be great.

Right now I selected Opcode Cahce, do you mean the setting is currently without any effect? If so I think activating it would be good.

So I used W3 Total Cache on one wordpress, and I selected Redis for caching (as it was one of the options).

Nevertheless, my website crashed over time, and looking at the console, I have errors regarding Redis all the time (this one is a sample):

Feb 12 11:30:40 [Tue Feb 12 11:30:40.186515 2019] [php7:notice] [pid 58] [client 172.18.0.1:41762] Redis server went away
Feb 12 11:30:40 [Tue Feb 12 11:30:40.188249 2019] [php7:warn] [pid 58] [client 172.18.0.1:41762] PHP Warning: Redis::pconnect(): connect() failed: Connection refused in /app/data/wp-content/plugins/w3-total-cache/Cache_Redis.php on line 351

To be honest, I don't have any idea if Redis is better than the other alternative (Opcode Alternative PHP Cache).

Quick note, since last release, there's a monocontainer version available.

https://docs.funkwhale.audio/installation/docker.html#docker-mono-container

This is a nice alternative to Ampache / Airsonic compatible with subsonic API, and with an ActivityPub touch.