EasyApache Profile customization
Completed
As a server administrator I would like the ability to customize my build, and then be able to save that build to a new custom profile (both in WHM and on the command line), in the same way that I could EasyApache 3, allowing me to (among other things) duplicate that profile across servers.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
This did get included in cPanel & WHM version 64, which is now in the CURRENT tier. Update now to take a look!
This did get included in cPanel & WHM version 64, which is now in the CURRENT tier. Update now to take a look!
This really makes a poor impression for EA4 coming from EA3. User interface touches such as this really matter.
This really makes a poor impression for EA4 coming from EA3. User interface touches such as this really matter.
This is really important when you have multiple servers and save time!
This is really important when you have multiple servers and save time!
This really would be helpful, having to mess around with json files can be awkward
This really would be helpful, having to mess around with json files can be awkward
I agree. I don't understand why developers could consider removing this ability would not be frowned upon. We pay you to make our job easier/efficient. How does forcing me to manually create CLI profiles when I am used to saving the same with the click of a button make my job easier or improve efficiency? Honestly some of the design/feature implementations cP has come out with do not pass a user friendly test IMO.
I agree. I don't understand why developers could consider removing this ability would not be frowned upon. We pay you to make our job easier/efficient. How does forcing me to manually create CLI profiles when I am used to saving the same with the click of a button make my job easier or improve efficiency? Honestly some of the design/feature implementations cP has come out with do not pass a user friendly test IMO.
Good morning,
As we've been working on bug hunting and fixing the past couple of releases, we're about to start working on profile selections and saving.
I think we're going to tackle this in a few ways:
UX: Not forcing users to go through all the steps of the UI to be able to save this as a profile
UX: When customizing currently available profiles, users will click 'Customize', and start making changes. Users will have a 'Save to new profile' button at the bottom of each wizard 'step', allowing users to save changes without having to go through the entire provisioning process
UX: Allows a user to easily take their currently installed stack and turn it into a profile with one button
UX: Should prompt for a name, desc, tags and allow to save into '/etc/cpanel/ea4/profiles/custom'
I'd love feedback on these if you have some free time!
Good morning,
As we've been working on bug hunting and fixing the past couple of releases, we're about to start working on profile selections and saving.
I think we're going to tackle this in a few ways:
UX: Not forcing users to go through all the steps of the UI to be able to save this as a profile
UX: When customizing currently available profiles, users will click 'Customize', and start making changes. Users will have a 'Save to new profile' button at the bottom of each wizard 'step', allowing users to save changes without having to go through the entire provisioning process
UX: Allows a user to easily take their currently installed stack and turn it into a profile with one button
UX: Should prompt for a name, desc, tags and allow to save into '/etc/cpanel/ea4/profiles/custom'
I'd love feedback on these if you have some free time!
Save and/or navigation options should appear at top and bottom of each page. User should never be forced to scroll up or down only to save.
Save and/or navigation options should appear at top and bottom of each page. User should never be forced to scroll up or down only to save.
Hiya,
We've gotten a few mockups of these new functions, and I wanted to share them here and see what you thought.
Note: What you see are just mockups, they most likely won't appear identical once actually implemented.
Hiya,
We've gotten a few mockups of these new functions, and I wanted to share them here and see what you thought.
Note: What you see are just mockups, they most likely won't appear identical once actually implemented.
Please have a feature to convert old EA3 .yaml profiles to the 'new'/'better' EA4 profile format. (This should have been the first step to keep users happy, and it would have shown you immediately design flaws. Always it is the compatibility issues that reveal so much.)
Also, the features are much more cumbersome to overview/overlook than before, because everything is totally bloated and uses endless space, instead of being neatly organized to view a lot/all on one page.
Further, to compare between versions what is installed, it would be good to have an 'inherit' feature, so that e.g. php extensions of v5.6 chosen are immediately selected also for any other version (if available, and if not, have a hint that they are missing there and how to alleviate this (last one is probly asking much)).
Perhaps go:
More ergonomics, less oversimplification.
Less bloat-ing, more neat-ing.
Less scrolling, more side-by-side table or columns.
Less radical changes, more gradual improvement (ie no cut out of features).
The 'non-recompile but RPM-use' - however - seems actually really good! :)
Please have a feature to convert old EA3 .yaml profiles to the 'new'/'better' EA4 profile format. (This should have been the first step to keep users happy, and it would have shown you immediately design flaws. Always it is the compatibility issues that reveal so much.)
Also, the features are much more cumbersome to overview/overlook than before, because everything is totally bloated and uses endless space, instead of being neatly organized to view a lot/all on one page.
Further, to compare between versions what is installed, it would be good to have an 'inherit' feature, so that e.g. php extensions of v5.6 chosen are immediately selected also for any other version (if available, and if not, have a hint that they are missing there and how to alleviate this (last one is probly asking much)).
Perhaps go:
More ergonomics, less oversimplification.
Less bloat-ing, more neat-ing.
Less scrolling, more side-by-side table or columns.
Less radical changes, more gradual improvement (ie no cut out of features).
The 'non-recompile but RPM-use' - however - seems actually really good! :)
Hey all! We're still aiming at version 64 for this, but it might not all make it. Once we get closer to the feature development cutoff (in about a month) we'll have more information.
Hey all! We're still aiming at version 64 for this, but it might not all make it. Once we get closer to the feature development cutoff (in about a month) we'll have more information.
This did get included in cPanel & WHM version 64, which is now in the CURRENT tier. Update now to take a look!
This did get included in cPanel & WHM version 64, which is now in the CURRENT tier. Update now to take a look!
Replies have been locked on this page!