I think creating a new ssl-vhosts.conf file is the right way. You can check Diablo925 first SSL module for that because it worked that way.
Storing all ssl files in one folder seems impractical. Adding the files to a seperate ssl folder within the account like the recent Diablo925 module makes more logic i think. That way account admins have acces to there files.
Automating Lets encrypt and selfsigned should be there. For account admins this should be one click setup. Sentora can run the lets encrypt script (wihout using the 80 port) and even add a cron for automatic renewal.
I think there should be a apache check yes. Maybe using the sanitiecheck of apache something like this:
First toughts there. gonna look deeper into it in the coming weekend.
Storing all ssl files in one folder seems impractical. Adding the files to a seperate ssl folder within the account like the recent Diablo925 module makes more logic i think. That way account admins have acces to there files.
Automating Lets encrypt and selfsigned should be there. For account admins this should be one click setup. Sentora can run the lets encrypt script (wihout using the 80 port) and even add a cron for automatic renewal.
I think there should be a apache check yes. Maybe using the sanitiecheck of apache something like this:
PHP Code:
function restart() {
$cmd = str_replace(' graceful', ' configtest', $this->apache_restart_cmd());
if ($this->server->shell_exec($cmd)) {
apache_log('Apache configuration is valid', 'ok');
parent::restart();
}
else {
// Set an error, so we'll roll-back.
etc
etc
etc
First toughts there. gonna look deeper into it in the coming weekend.