If that custom app is a php app, you may be able to use the LAMP app. Otherwise you can package it up as a Cloudron app (mostly as a docker image, with some Cloudron specific meta information and behavior) That process is somewhat described at https://cloudron.io/developer/
@mishkalidas When there is an update, you will see an update button in the UI. This is the same for apps - when there is an update, you will see an update indicator in the app grid. There is no other supported update mechanism. Let me know if I misunderstood your question.
Okay, that makes sense. Thank you for the quick reply. 🙂
I wonder if it would make sense to add a feature where we can set the IP address to accommodate floating IP's in providers like DigitalOcean, so that the DNS records automatically setup by Cloudron in DigitalOcean would be using the floating IP instead. Without such a feature, it kind of removes the ability to have a sort-of manual failover method which is one of the main purposes of a floating IP from DigitalOcean (along with a secondary use-case of setting up a new server to replace an old one and moving the floating IP to the new one when ready, eliminating the need to update a whole bunch of DNS records). It would be nice, I think, to have Cloudron use a floating IP that we give it even if it means we have to set it manually in Cloudron first since it can't detect it automatically. The main reason for this is that whenever I switch a server, for example, nothing really needs to be changed at all, leaving downtime to a minimum if it exists at all during a server switch.
We already implemented a mechanism wherein if the userId and the domain name matches, you will get subscribed to any previously subscription. If you have to change the domain, currently the only way is to contact support and give us the new cloudronId. @dustinddotca I guess you changed the domain name? Can you please send the new cloudronId to email@example.com, will be happy to refund and transfer existing subscription.
The version you are referring to is correct. So far we have stayed in-sync with ubuntu security updates, but probably have to revisit this and see if nginx can and should be indeed updated individually.