Hi,
according to the official Administrator's Guide (Appendix A: Ressources), the 'disk space' value in a service plan definition "includes disk space occupied by all files related to the subscription: content of websites, databases, applications, mailboxes, log files, and backup files."
Additionally it's possible to set a hard quota (in supported) in 'hosting parameters'. According to the Guide (Appendix A: Hosting Parameters) "Hard disk quota will not allow writing more files to the web space when the limit is reached"
There is an obvious difference in the wording. While the first explicitly states, that all files are included into the calculation, the definition for the hard quota only speaks about the 'web space', which would be, as I understand it, only the contents of /var/www/vhosts/<domain>/httpdocs.
Since mails and databases are saved as other users (popuser/mysql) this also makes sense, however I'd like to confirm it.
Is anybody using hardquota and can tell, which files are used for the calculation?
according to the official Administrator's Guide (Appendix A: Ressources), the 'disk space' value in a service plan definition "includes disk space occupied by all files related to the subscription: content of websites, databases, applications, mailboxes, log files, and backup files."
Additionally it's possible to set a hard quota (in supported) in 'hosting parameters'. According to the Guide (Appendix A: Hosting Parameters) "Hard disk quota will not allow writing more files to the web space when the limit is reached"
There is an obvious difference in the wording. While the first explicitly states, that all files are included into the calculation, the definition for the hard quota only speaks about the 'web space', which would be, as I understand it, only the contents of /var/www/vhosts/<domain>/httpdocs.
Since mails and databases are saved as other users (popuser/mysql) this also makes sense, however I'd like to confirm it.
Is anybody using hardquota and can tell, which files are used for the calculation?