Make "At top level" default installation path for additional scripts

When you click on "Install Scripts", choose any script, for example, phpMyAdmin, then it always offers to install the script on sub-directory under public_html by default. I'd like to request to make "At top level" option set by default, because most of the time users create separate virtual server for the programs listed in "Install Scripts" and they are always confused why they scripts got installed in subdirectories.

It would be also nice if some scripts would use default database for their respective virtual server instead of creating additional one. For example, if you click on "RoundCube" it always offers to create new database with "_ roundcube" suffix in the name. Thus an empty database (default to virtual server) are always left. Well, suggesting new database is good in case if the default database has been already used, but making it default option is not good. Leave suggestion for creation new server as an option, by leave the existing database as the default one.

I hope what I suggest make some sense. Thank you!

Status: 
Closed (fixed)

Comments

That's not a bad idea - I will look into implementing this.

Keeping scripts to separate databases is a good idea though, as it means that when the script is un-installed the database can be safely dropped without risking data created by other applications.

The 4.01 release of Virtualmin will let you change the default install directory for scripts.

There is a setting at System Settings -> Virtualmin Configuration -> Advanced Options -> Template for default script directory that should allow you to set this, but it doesn't work in the current release. That will be fixed in version 4.01 though.

Thanks Jamie!

It is not clear how to set top level, though. The description for this option says: Template for default script directory

By default Virtualmin will install new scripts into a sub-directory with the same name as the script code, like phpadmin. This field lets you enter a template for a different default directory, like scripts/${SCRIPTNAME}. All the usual template variables like ${DOM} and ${USER} can be used as well.

Edit: I just noticed I have still version 3.99. When 4.01 is coming? There is no any upgrade available currently.

In the 4.01 release, that field will have an additional option to install into the public_html directory.

That version is likely several weeks off though, as 4.00 is still in the process of being tested and released.

Automatically closed -- issue fixed for 2 weeks with no activity.