What's coming in Cloudron 7.1
-
@timconsidine possibly they were using CloudronManifest version 1, which was deprecated for some time now and got removed with 7.1
What this means is, that the injected env vars will now always be prefixed withCLOUDRON_and maybe your custom apps were still looking for example forMYSQL_HOSTinstead ofCLOUDRON_MYSQL_HOST? -
7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).
@girish said in What's coming in Cloudron 7.1:
7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).
I triggered a manual update check before coming across this post. Is there a way to tell cloudron to skip this update or stop it from auto-updating?
-
@girish said in What's coming in Cloudron 7.1:
7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).
I triggered a manual update check before coming across this post. Is there a way to tell cloudron to skip this update or stop it from auto-updating?
-
@girish said in What's coming in Cloudron 7.1:
7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).
I triggered a manual update check before coming across this post. Is there a way to tell cloudron to skip this update or stop it from auto-updating?
@humptydumpty I believe that updating to 7.1 can only be done manually and will NOT happen through auto update (if with auto update enabled).
-
@humptydumpty I believe that updating to 7.1 can only be done manually and will NOT happen through auto update (if with auto update enabled).
@avatar1024 that is correct, releases which are not yet put out for all users, will not be auto-updated. Our current approach is, to first make a release for new installation and people who would like to manually update to it. Then if things look good, we will slowly roll it out for auto-updates (if enabled on a Cloudron) over around a week or so.
-
@nebulon I still have 2 custom apps running on manifestversion 1, what will happen to them if I upgrade before updating those apps?
-
@girish said in What's coming in Cloudron 7.1:
Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support
AAAArecords. There is a checkbox in the Network view to enable the IPv6 support.This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.
We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.
@girish said in What's coming in Cloudron 7.1:
@girish said in What's coming in Cloudron 7.1:
Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support
AAAArecords. There is a checkbox in the Network view to enable the IPv6 support.This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.
We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.
Just updated to 7.1.2 I noticed I had to 'save location' of the apps to add the AAAA records. However the mailserver and Cloudron access URL still don't have AAAA records, not even after restarting the mailserver. Is this expected?
-
@girish said in What's coming in Cloudron 7.1:
@girish said in What's coming in Cloudron 7.1:
Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support
AAAArecords. There is a checkbox in the Network view to enable the IPv6 support.This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.
We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.
Just updated to 7.1.2 I noticed I had to 'save location' of the apps to add the AAAA records. However the mailserver and Cloudron access URL still don't have AAAA records, not even after restarting the mailserver. Is this expected?
@imc67 you have to go to Domains -> Sync DNS records for the existing apps/mail server.
Before you suggest it, yes, we should probably do this when IPv6 is enabled
As a heads up, there is also a quirk that if you disable IPv6, the AAAA records are not removed by the sync . -
@girish said in What's coming in Cloudron 7.1:
Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support
AAAArecords. There is a checkbox in the Network view to enable the IPv6 support.This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.
We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.
@girish said in What's coming in Cloudron 7.1:
@girish said in What's coming in Cloudron 7.1:
We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.
AMAZING WORK! From our exceptional professional and cutting edge team of developers at Cloudron, should it be said once in a while.
Thanks for your fantastic work @girish @nebulon guys you are simply the bests.
-
G girish unpinned this topic on
-
G girish locked this topic on
