Otherwise I feel we still have to discuss the notification system then to also work for your use-case. Maybe you can start a separate thread describing what your ideal solution would look like a bit and we can see how this makes sense for us to implement this way or not.
@d19dotca I'm looking forward to that too, but mail is not so critical for me.
I spent ~10 hours earlier this week getting Papercups up and running on a separate VPS. If it were on Cloudron, it would have been 5 mins plus config. So - for me at least - mail is a bonus, with core case for Cloudron proved day in day out.
@cyberfreakde no, the server and apps won't stop and will continue to run forever. Additionally, no features are disabled as such. The main change is that you cannot install more apps and existing apps won't get updates. I put these notes in https://docs.cloudron.io/billing/#canceling-subscription . Also, support is limited if you let the subscription lapse too much (hard to support if software is outdated by many releases).
@marcusquinn it's an interesting option to have available for Cloudron.
I haven't researched whether there would be bandwidth issues for the deployed instance, serving out video. Maybe they have a clever way to minimise load on the hosting server.
@yeku I understand the points, but I have only seen a couple of errors, and they haven't prevented me getting the message or successfully using Cloudron.
I think Cloudron have enough work running a fantastic architecture. The community here can help out @girish free of charge with great enthusiasm. Errors just need to be reported and they can be fixed quickly.
@marcusquinn Yeah. I was in a fraternity when I was in college. It was like the movie Animal House... but worse. Looking back on it I'm embarrassed by what I did. But it was fun at the time. College itself was a big waste of time for me.
To be fair, you will get the same footprint with a multi-stage build and images that depend on the same shared base.
Let say that we will have a CloudronBase (Image LVL1), this image will include only ubuntu + minim software used for debugging.
As a second step you will get different images with all the dependencies for the different cases:
One image for every type of DB: MariaDB, pSQL, MongoDB.
One for the webservers: Nginx, and Apache (that can maybe already include PHP).
Then as the last level (3) of images, we have the language, like: node, python, etc, etc.
This will have the same footprint as the one big image that we have now, it will always be a Cloudron Base, but it will be like:
Yes to slit the image in multiple parts will be a big work, but then we can update all the lvl with less effort.
And as a second bonus, we will be able to have a server with just 2 WordPress, without unused library and software.
To resume, what I propose is to keep the idea of an cloudron base, but to slit it, so that the apps can be developed easily, but servers with 20 GB of storage don't louse 10% of their space for code that they will never use.
@necrevistonnezr click on the command(s) that interest you, that takes you to another page.
On the first one - bat - the install instructions are right at the bottom (lots of scrolling)
Didn't look at the others yet.
Good point... I checked if there is a way to say "only notify users subscribed to this post" when creating a new app update post but that option is not there on NodeBB. Looks like as @thetomester13 said, the onus is on the reader to actively "ignore" update posts.
@scooke Interesting. The certificate and the PTR record check shouldn't have anything to do with each other. The PTR record check is really just dig -x IPADDRESS . Can you try that say 10 times over the course of an hour with your VPS server IP and see if it's consistent?
As for old certs, they are indeed preserved forever even if you remove the domain from Cloudron itself but the latest release will now clean up obsolete certs which are 6 months old.