12.26.0 now available

Aliysa_Enhance

Added
Deploy via GitHub:

You and your customers can now manually or automatically on push deploy public or private repositories from a connected GitHub account to new or existing production or staging websites.
Deploy via GitHub can be performed via the ‘add new website’ flow, directly from the account-level connection (left hand spine) or from the GitHub section in the website management dashboard.
Documentation can be found here.

Worker processes:

It is now possible to run PHP, Node.js, Laravel, static websites and Custom Applications (for instance a runtime built in Rust or Go) worker processes.
UI support is available under the ‘Worker Processes’ section on the website management dashboard.
A ‘Platform details’ card on the MOs and Resellers dashboard now highlights key information including: Control panel URL, Webmail URL, Staging domain suffix, phpmyadmin URL and nameservers for that account.

Enhanced

Improvements to internal locking strategy to improve the speed of website dashboard operation.
The Node.js section of the panel has been replaced with “Worker processes”, allowing for non-node applications to be started and managed by Enhance such as Laravel workers.
‘Users’ has been renamed to ‘Team’.
‘Packages’ in the customer dashboard (showing the packages to which the customer has been subscribed) has been renamed to ‘Subscriptions’.

Fixed

Mitigation for wp-cli invocation issue where passwords containing ’ would be rejected on initial WordPress installation.
Quota and cgroup changes to a non-reseller plan where the user is also subscribed to a reseller plan will no longer propagate to the reseller’s customers.
Where a secondary domain mapping fails due to unavailability of the web server, the new mapping is no longer recorded in the control panel database.
Improved nvm installation script to prevent potential overlap/concurrency issues.

slimx

Aliysa_Enhance The Node.js section of the panel has been replaced with “Worker processes”, allowing for non-node applications to be started and managed by Enhance such as Laravel workers.

Interesting, we run lots of laravel apps cant wait to try it!

DracoBlue

Updated without any issues. Now I'm just waiting for support for upgrading to Ubuntu 26.04 and Roundcube 1.7.x.

wav3front

congrats !

ecomlabs

Congratulations to the entire team and the community. Furthermore, @cPFence has now reached version V4; this marks a major turning point for our clusters. @cpf

Splunge

Have to say, not sure how much work you guys have put into the 12.26.0 but the UI for launching apps, and the github additions are just sick! I really look forward to playing with these features a bit more shortly.

And ecomlabs , I haven't updraged to v4 cpFence yet as I thought it was still in RC stage. If it's been rolled out, will definitely upgrade the cluster later this week. Well done all! 😁

bluelinq-computers

Excellent update. No issues updating. And yes, @ecomlabs @cPFence v4 is a huge step in management for enhance servers..

pratik_asabe

kudos to the team! we were eagerly waiting for github auto deploy, this solves so many issues and open many opportunities for us, especially when most of our clients use ci workflow, we can now manage them in same cluster instead maintaining separate non-enhance servers!

elcapitanph

@Adam thank you and your team Finally hahaha. do you guys talk with cpfence , @cPFence also update to v4 and i tested and it's work good. but still checking

mike

I guess i want to try the the new version esp the worker … but not today 😏

Vendoz

Great update, finally 🫶

Just a quick feedback: in the new section "platform details", the Webmail URL should be hidden if no email service is present, rather than displaying mail.(client-domain.com) 🤗

Aliysa_Enhance

Vendoz Thanks! This should absolutely be contextual. We'll inlude this fix in an upcoming update.

PDudeP

Aliysa_Enhance

Under Emails > Email Client Setting, would it be possible to show mail.client-domain.com instead of the hostname of the email server?

That generates lot's of issues, if a clients email accounts are migrated to another server...

CamielK

PDudeP
+1
I'd also like to be able to create a global webmail domain without it being forced to be used on Roundcube SSO in the panel and all other places. mail.customerdomain.tld should always be the primary (web)mail domain

Adam

PDudeP

Remove the SHN domain mapping from the website list, then customers will be shown mail.$customerdomain. If you need the SHN domain for DNS you can add the record within the parent zone instead.

PDudeP

Adam

Thanks, @Adam . I ended up removing the SHN, and it did the trick.
I tried adding it to the parent DNS zone, but it didn't work.
No worries, I'll keep it like that.

Thanks

btraill

Amazing... very thankful for this update. Thank you Adam & team.