I would like to have a file manager in WHM. (like ConfigServer Explorer) .Thanks.
Max
WHM File Manager with access to /
Open Discussion
Customers like to be able to browse all of their files outside of /home/{cpanel_user}.
Examples are:
* /etc/my.cnf
* /var/log/*
* /backup/* to see the dates of backups
Many other examples.
Hoping it's not too much work to adapt the cPanel File Manager to make it work inside of WHM for the entire /.
(similar to how there's both a phpMyAdmin for both cPanels and WHM)
Thanks
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 would be a great addition! There are plenty of customers who are not comfortable (or just don't want to) learn how to use SSH. Implementing something like this would remove a large frustration for all those users.
This would be a great addition! There are plenty of customers who are not comfortable (or just don't want to) learn how to use SSH. Implementing something like this would remove a large frustration for all those users.
A great many time customers want expanded features of WHM however have no ability to manage ROOT only services like Removing backups or changing MySQL user connections. This would go along way to a more usablility to "softcore" users.
A great many time customers want expanded features of WHM however have no ability to manage ROOT only services like Removing backups or changing MySQL user connections. This would go along way to a more usablility to "softcore" users.
This can lead to major security issues. As more of a technical person, I'm adamantly against this idea. As far as backups are concerned, this would be a more appropriate extension of the backup features in cPanel. Having file manager access / is a disaster waiting to happen.
This can lead to major security issues. As more of a technical person, I'm adamantly against this idea. As far as backups are concerned, this would be a more appropriate extension of the backup features in cPanel. Having file manager access / is a disaster waiting to happen.
You can't actually be serious?
I do not feel this should be a feature of the WHM product. There is many ways this could be abused or lead to serious issues with the server. If you really want this google "ConfigServer Explorer (cse)".
You can't actually be serious?
I do not feel this should be a feature of the WHM product. There is many ways this could be abused or lead to serious issues with the server. If you really want this google "ConfigServer Explorer (cse)".
NOTE: we're only talking about customers who login to WHM with the username root; nothing else!
NOTE: we're only talking about customers who login to WHM with the username root; nothing else!
Shold a user who can't manage basic command line editing be allowed a graphical editor in which it's very easy to move or delete files by mistake. I've voted against this for the same reason as we don't allow root FTP or SFTP access.
Shold a user who can't manage basic command line editing be allowed a graphical editor in which it's very easy to move or delete files by mistake. I've voted against this for the same reason as we don't allow root FTP or SFTP access.
While I can appreciate security concerns, many customers want to be able to see and manipulate the file system, whether it be backups or files within different home directories. If you give a customer root privileges, they have full access to the system anyway and as such they have to understand that they can have the ability to screw things up. So I see a WHM-based file manager as an extension to that.
WHM is supposed to make things easier - not dumb things down sufficiently that it makes life more difficult. It's the customer data, they'll need to take responsibility - and it's the hosting provider's responsibility to put across to the customer that the root user can do significant damage if they're not careful.
While I can appreciate security concerns, many customers want to be able to see and manipulate the file system, whether it be backups or files within different home directories. If you give a customer root privileges, they have full access to the system anyway and as such they have to understand that they can have the ability to screw things up. So I see a WHM-based file manager as an extension to that.
WHM is supposed to make things easier - not dumb things down sufficiently that it makes life more difficult. It's the customer data, they'll need to take responsibility - and it's the hosting provider's responsibility to put across to the customer that the root user can do significant damage if they're not careful.
I'm against root access file editors for the same reasons why you shouldn't use sftp root access.
The first thing I do when I log in to ssh as root is su to the correct user to not be able to edit / delete a file owned by another user by mistake.
In my oppinion sysadmins find file related commands faster and easier than using a web based editor. Should non sysadmin people have access to system administration files ?.
I'm against root access file editors for the same reasons why you shouldn't use sftp root access.
The first thing I do when I log in to ssh as root is su to the correct user to not be able to edit / delete a file owned by another user by mistake.
In my oppinion sysadmins find file related commands faster and easier than using a web based editor. Should non sysadmin people have access to system administration files ?.
The likelihood that we implement a File Manager with the ability to browse any arbitrary system-level files as root is pretty low HOWEVER we are much more apt to creating interfaces with syntax-highlighted code-editors for specific configuration files within the relevant sections of the WHM Interface. You can already see an example of this with the PHP INI editor found in EasyApache 4.
The likelihood that we implement a File Manager with the ability to browse any arbitrary system-level files as root is pretty low HOWEVER we are much more apt to creating interfaces with syntax-highlighted code-editors for specific configuration files within the relevant sections of the WHM Interface. You can already see an example of this with the PHP INI editor found in EasyApache 4.
Integrated file managers have caused no end of problems, just in the cPanel user interface let alone the potential for catastrophic errors in the WHM interface. So Voting No.
Integrated file managers have caused no end of problems, just in the cPanel user interface let alone the potential for catastrophic errors in the WHM interface. So Voting No.
That would be great. I need to move files between two domains that I own, I need for example this:
[user1@ip-xx-xxx-xxx-xx Folder1]$ pwd
/home/user1/public_html/domain/Folder1
[user2@ip-xx-xxx-xxx-xx Folder2]$ pwd
/home/user2/public_html/domain/Folder2
[user2@ip-xx-xxx-xxx-xx Folder2]$ cp *.* /home/user1/public_html/domain/Folder1
and this is not possible...
That would be great. I need to move files between two domains that I own, I need for example this:
[user1@ip-xx-xxx-xxx-xx Folder1]$ pwd
/home/user1/public_html/domain/Folder1
[user2@ip-xx-xxx-xxx-xx Folder2]$ pwd
/home/user2/public_html/domain/Folder2
[user2@ip-xx-xxx-xxx-xx Folder2]$ cp *.* /home/user1/public_html/domain/Folder1
and this is not possible...
Replies have been locked on this page!