You guy are are amazing and fast, thank you! 🙂

yes, that tag-input component has several other small bugs and we should really replace it. If anyone knows a good angular1 based component to replace it, ideas welcome 🙂

This comment was very informative - https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/comments/6 . I didn't realize you have to pass so many options to make it not ask questions.

Also, note that changing the nameserver sometimes takes a bit of time. So, you might have to wait a bit between step 2 and step 3.

I was unaware of the incremental feature in rsync. That will work for me, thank you!

Looks like it was in fact getting sent to the catchall. Thanks everyone for your input.

@necrevistonnezr Yeah you can click the search icon in the UI, then in the select box, change to "Entire Message" and it searches both the headers, the body, and in some cases attachments as well (in the case of txt attachments I think? I've never had a need for it and no real way to test it)

925fe9c5-e509-4f0a-af70-682114ec4f24-image.png

I have 18 differents domains with 46 apps at present.

As of now, I don'(t extensively use tagging, because the tag selector is a multiselect, which means I have to unselect my previous selection to switch context, which is too much trouble for me to use.
I don't really use domain switchign because, selection with dropdown is a bit awkward to work with once you have a pretty long amount of items. (and it resets once you quit the page)

So I haven't been really happy with the way it works.

Thinking about it, a structure like the App Store, but configurable would probably be a pretty decent way organizing it.
The default homepage could show Favorite Apps (instead of "Popular"), Tags instead of "Categories" and with a "Search" and "All" filter, we could get all sorted. (pun intended^^)

What would also help would be to have the app meta fields (tags, label and maybe icon) show up before you click install/clone.
Also, when an app in installed/cloned, it is viewable on every user dashboard, regardless of groups. The access settings can only be done afterwards. So there's a, arguably small privacy issue here. Access should ideally be configurable before app is installed.

With those two changes, everything (permissions and meta) could be setup and correctly categorized when the app is installed.

I have no idea how many apps are typically installed on a cloudron, I can totally understand this structure wouldn't be worth it for users with a limited number of apps.
Though the permissions and meta fields setup at app install/clone time is relevant in any case.

Finally, there would be a case for merging groups and tags, so users relating to a group can access all apps tagged in this group. Maybe it's a bit too rigid and this is probably a wider conversation because it also encompasses users, emails etc.

Done, added notification for the next release.

@njha The Cloudron version of minio is intended for hosting static file assets and not as a backup destination for Cloudron itself. If you want to backup Cloudron to minio, we recommend setting up a separate non-Cloudron server that just runs minio that proxies to b2.

@lunarshade Can you give some idea on what you are trying to customize? If these are general UI/UX improvement, we are happy to incorporate them into the main product itself.

If you are a hosting provider, we are building out customization features in the hosting provider edition - https://cloudron.io/documentation/hosting-provider/ (write to us at support@cloudron.io for a trial license)

Yes, if that is going to be an option soon then we can mark this as resolved 😄 Thanks!

@stoccafisso I have put this in our 4.1 roadmap - https://forum.cloudron.io/topic/1789/what-s-coming-in-4-1 . The feature is already supported in our backend (dataDir field when calling the configure route) but the UI is hidden. We will work on making it public.

That's good news. I suspected nothing was compromised with Cloudron but it's good to have it stated. 👍

Just a heads up. The next release will include initial tag support for apps and thus filtering based on tags in the dashboard as well as allowing to specify a display name for each app, instead of the current subdomain/domain.

I use it since month's without any problem, I git pulled the code into the public folder..

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

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.