The description on Excluded Directories and DBs page says:
By default, Virtualmin will include all data in a servers's home directory when making a backup. However, if a domain has files that are too large to include or are backed up via some other method, this page can be used to exclude them from backups.
which is good, but useless unless configured per website. And often times end-users are too confused/indecisive/lazy to configure this exclusion page. So we would like to be able to configure this on a server-level, for example in templates, so that when the virtual servers (domains) are created the excluded files and directories were already there by default. That would be especially useful for hosts that mostly deploy certain software, like for example CMSs like Drupal or Wordpress, and know the directory structure even before the websites are created.
This is a feature requests, however if there are some ways of achieving this without introducing any new feature then please explain how to do so.
Thanks for consideration!
Comments
Submitted by JamieCameron on Thu, 08/10/2017 - 14:12 Comment #1
That sounds like a good idea - would you prefer that it be configured per-template (and so could be changed after domain creation) or globally?
FYI, you can use the Virtualmin command-line API to mass-set the excluded directories for all existing domains if you want.
Submitted by yngens on Thu, 08/10/2017 - 19:27 Comment #2
I don't know, Jamie, what do you think would be better option for most of the Virtualmin users out there? The main idea is to exclude all the commonly used large archive and compressed files, some frequently used (by popular CMS like Wordress, Joomla, Drupal) large cache databases by default, and not to be dealing with this on per virtual server post their creation.
Submitted by yngens on Thu, 08/10/2017 - 19:28 Comment #3
That's very good to take note of. But it would be much better to pre-configure this than to deal with this after creating virtual servers.
Submitted by JamieCameron on Fri, 08/11/2017 - 11:01 Comment #4
Ok, I will look into making this a template-level default for new domains.
Submitted by JamieCameron on Fri, 08/11/2017 - 18:53 Comment #5
Ok, this has been implemented for inclusion in the next release.
Submitted by JamieCameron on Fri, 08/11/2017 - 18:53 Comment #6
Submitted by IssueBot on Fri, 08/25/2017 - 18:56 Comment #7
Automatically closed - issue fixed for 2 weeks with no activity.