This may be the first of a few questions. I am currently evaluating control panels for staff to use for our organization only.
Great product so far! Beating out the "other" common LAMP panels by far.
I want to turn off ProFTD completely and only allow SCP access for upload of website files to some of our staff in other departments. We are running the test sites under FCGId which when combined with SuExec requires files to not be Group writeable, as I understand it. This poses a problem for users that I create in VirtualMin and give Email and SCP access levels.
These additional users can certainly read files in the public_html directories but since folders are 755 and .php scripts 644, they are unable to write to the directory.
Am I missing fundamental here?
Many thanks. I'm getting close to pulling the trigger on this purchase but need to get through a few other hurdles in proof of concept mode.
Blessings,
Tom
Howdy,
It's no problem to disable FTP. That's a good, and secure, thing to do!
However, normal users don't typically have rights to write to the website DocumentRoot, without a little file permission tweaking.
An alternate way to do that, is to create a "Website Access FTP User" (in Edit Users) -- and although it says "FTP User", you'd just need to make sure those users have a valid shell, such as /bin/bash.
If a user has a valid shell, they'd be able to login via SSH.
Note though that those Website Access users are only designed for modifying web sites, they wouldn't have email.
If you wanted an existing user, who has an email account, to be able to modify websites, you'd have to change the files and directories within the DocumentRoot so that they were group writable.
Does that make sense?
-Eric
Great. Thanks Eric. Yes, that seems to make sense. So I was able to accomplish this with an FTP user and then create a custom shell mapping.
I'm starting to see that the custom shell mappings are then made available in the user edit page under the permission section. Seeing the relationship helps.
Now, while doing trial and error in the custom shell section, I've really made a mess of the defaults. :( Enabling the built-in VirtualMin shell selections and then re-enabling custom did not reset the custom to what the base install had. Sooooo.... is there a way to put the custom shell mapping back to what it should be out of the box or documentation on the what the defaults are? It's not critical since this is just an box for eval purposes and we'll reinstall on a new box when we make a purchase decision.
Another question. If I go with VirtualMin Pro on one box and GPL on another box, can I simply upgrade the GPL to a Pro license if needed later or do we have to reinstall the pro version from scratch?
Lastly, does the Pro install script support Ubuntu 12.04 LTS?
Many, many thanks and blessings to you,
Tom
Got my answers on Upgrade GPL to Pro. Got my answer to install script on Ubuntu 12.04.
Thanks