{"id":45485,"date":"2017-06-15T10:00:00","date_gmt":"2017-06-15T15:00:00","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=45485"},"modified":"2017-06-15T10:00:00","modified_gmt":"2017-06-15T15:00:00","slug":"june-development-update","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/june-development-update\/","title":{"rendered":"June Development Update"},"content":{"rendered":"

We’ve pulled the cPanel mobile apps from the store, but retained these posts for historical accuracy<\/i><\/strong><\/p>\n

The month of June is all about putting the finishing touches on version 66, and getting started on version 68. Version 66 hit Feature Freeze last week (take a look at\u00a0this post about the cPanel Development Process<\/a>\u00a0if you aren’t sure what that means), so we know what features will and will not be in version 66. We went into planning for version 68 just a few weeks ago, and our teams are starting work on that as well. Two versions in development while ramping up planning the cPanel conference means we have a whole lot to talk about. Let’s start with a quick rundown of some of the things I’m most excited about that\u00a0we didn’t talk about last month<\/a>.<\/p>\n

Application Manager<\/h3>\n

One of our development teams has been working on a new feature that we’re calling Application Manager. The Application Manager allows you to deploy and maintain your Ruby applications with ease.<\/span>\u00a0In this first iteration we’re adding support for an updated and cPanel-provided version of Ruby (version 2.4.1), and an\u00a0<\/span>EasyApache 4 Passenger (version 5.1.2) module. Our goal is to be able to expand the Application Manager beyond just Ruby applications to provide support for additional languages (<\/span>Node.js<\/a>\u00a0anyone?). In this iteration there is <\/span>some work that needs to be done by root<\/a>\u00a0in order to enable the Application Manager, but in future version we’re planning to make that a bit easier.<\/span><\/p>\n

\"Application<\/a><\/span><\/p>\n

If you develop Ruby applications, this feature is built specifically with you in mind. Take a look and let me know what you think of it in a comment below, or by sending me a tweet<\/a> or an email<\/a>.\u00a0<\/span><\/p>\n

AutoSSL Domain Management in cPanel<\/h3>\n

AutoSSL is one of the most widely adopted features we have, and we want to give more control to the cPanel user. With version 66 cPanel users can choose to exclude their domains from AutoSSL inside the SSL\/TLS Status<\/a> interface of cPanel.<\/p>\n

\"AutoSSL<\/a><\/p>\n

WHM users will also be<\/span> able to manage those settings, either through cPanel or by using the related API calls on the command line. Another widely requested feature is the ability to prevent certain domains<\/a>\u00a0from being issued SSLs through AutoSSL as a root or reseller user. If you are interested in that, definitely vote and share your use-case there!<\/p>\n

PHP-FPM enabled by default, conversion for all accounts, and config scripts<\/span><\/h3>\n

We’re continuing to improve our PHP-FPM support<\/a> in 66 by adding two new options. First you will be able to set PHP-FPM as the default PHP handler, rather than having to manually enable it after account creation. This includes a dialog box in the interface that helps root users. Second, we’ve added an option in the WHM interface, an API call<\/a>, and a flag to the\u00a0command line php_fpm_config<\/a> script for converting all of your existing accounts to PHP-FPM with Apache.<\/p>\n

\"FPM<\/a><\/p>\n

We’ve also added a new\u00a0php_fpm_config<\/a>\u00a0script.\u00a0After any manual edits to the\u00a0PHP-FPM<\/a>\u00a0configuration files, run\u00a0\/scripts\/php_fpm_config<\/code>\u00a0to install those configuration files.\u00a0You can also use this script to troubleshoot problems in the FPM system. The obvious next step is to be able to more easily configure a wider range of PHP-FPM settings on a per-account basis. To keep tabs on when we do that, subscribe to this feature request: Enhanced PHP-FPM Configuration<\/a>.<\/p>\n

Full EasyApache 4 Profile Management<\/span><\/h3>\n

With version 66 we’re rounding out the EasyApache 4 Profile Management in WHM. You can now easily convert your existing EA4 build into a profile, upload a profile that you have, and download any<\/strong> EA4 build\u00a0profile on your server.<\/p>\n

\"EA4<\/a><\/p>\n

WHM UI (User Interface) Improvements<\/h3>\n

Over the last couple releases we have been making significant progress in reducing WHM’s reliance on frames. In version 66 we have eliminated the last few completely,<\/span>\u00a0which is making WHM on mobile devices much easier to use, and significantly improving the experience in the cPanel App (now in both iOS<\/a> and Android<\/a>). Many plugin developers are working with our team to get things updated and working correctly in a frameless WHM UI. Our UI team is taking a little break from making changes to WHM in the 68 development cycle to let them catch up, and to address any bugs that come up as part of this big back-end change.<\/p>\n

WHM Usability Improvements<\/span><\/h3>\n

There are a couple extra things that we were able to fit into cPanel & WHM version 66 as well, which will hopefully reduce the reliance on mouse clicks for some of our users.<\/p>\n

First, a large portion of cPanel & WHM servers are only hosting a single cPanel account. Historically, even in those situations many of the WHM interfaces that would make you choose that account before being able to proceed with the next step. Those WHM interfaces no longer prompt for you to pick a user if you’re on a server with only one user.<\/p>\n

The <\/span>existing keyboard shortcuts in WHM<\/span><\/a> are also being expanded in version 66, and will include the collapsing and expanding of the sidebar in WHM. It’s pretty slick.<\/span><\/span><\/p>\n

<\/a><\/span><\/p>\n

Deprecations<\/h2>\n

We only have a few new deprecations<\/a>\u00a0in version 66, but I want to make sure we talk about them.<\/p>\n