It's all webmail. Those are just application names.
Yes good catch just forgot how fast all changes ))It's all webmail. Those are just application names.
Like Outlook, Thunderbird, Eudora... it's all e-mail clients, just different applications to use with e-mail.
Roundcube is also webmail just different application to use it with.
Good question. I would also like to know if this will break a server. Or does DA simply stop releasing updates for it.What will happen with servers running any of them after DA drops support of them?
The only OS supporting mod_ruid2 is CentOS7. Without mod_ruid2 it runs under apache user, and is not recommended to run it like this. We'd recommend switching to another mode of PHP.Many of my customers are still using mod_php. On a dedicated server this is a fine choice I think.
It shouldn't, unless you mean a backupOn some servers with many GB's of data, updating MariaDB takes more than 6 hours.
It's controlled by a singlePlus, new rules in higher versions of MariaDB possibly will break website(s).
We're talking about end-of-life versions of MySQL/MariaDB, they are end of life not for "just months".All I am saying is that it would be nice to have these support issued noticed a year up ahead or so, not just months
With every hot-fix or update.Since 2 days I am getting three messages on one of my servers (CentOS 7 of course):
1) New Message: Your MySQL/MariaDB version 10.2 is EOL
2) New Message: Removal of mod_ruid2
3) New Message: Removal of mod_php
Are we going to get these mails on every server every day?
Can you relate to what happens to servers running unsupported PHP methods and webalizer?With every hot-fix or update.
It was just a question about webalizer/squirrelmail There is no final decision on them and no removal dates.Can you relate to what happens to servers running unsupported PHP methods and webalizer?
Ok, I'm using custom templates so it shouldn't be a problem. But is there any chance of an option "other" to ./build php_expert... ? The point is that CB will not overwrite any configurations outside of compiling a specific PHP version.Regarding PHP - CustomBuild/DirectAdmin won't support configuration of it, if you have custom configuration set there it'd work, but it'd stop working with default configs.
Please make sure there are no if clauses for mod_php, as they wouldn't work anymore It'd need to be hardcoded to be mod_php. Also, keep in mind that no other systems, but CentOS7, support it. CB won't have any native ways to install mod_php anymore. I'd like to note that after 2024, when CentOS7 becomes EOL, it'll have no use cases at allOk, I'm using custom templates so it shouldn't be a problem.
I'm only thinking about suPHP. For me, it's the best solution, super simple (and therefore stable) and safe. It has a built-in chroot (not via bubblewrap like in fast cgi), we also extended it with additional things like user limiting (CPU, number of processes). We can have dozens of different PHP versions (if we want, of course) that we enable/disable/replace in one configuration file (suphp.conf) and the user selects the version via one .htaccess line (also for subdirectories). Really many advantages. I know that there is also php-fpm and they also have their advantages (like lower CPU usage, although imo suPHP's poor performance is a bit of a myth). But migrating multiple servers (tens of thousands of vhosts) to another method of running PHP is a big problem.Please make sure there are no if clauses for mod_php, as they wouldn't work anymore
Recently Direct Admin checked its license and updated itself, while I dit not want any updates, since it is CentOS 6.How can we stop DirectAdmin auto-update itself ?
Are you sure ? this will be an big problem for use, but when i check the list of removed software I dont see LE ?Now they updated, some things stopped working, and I need to do things manually (Let's Encrypt for instance).
Sure! I had disabled updating directadmin on CentOS 6 servers, because there was a message like 'future updates may not work' etcetera, so I stopped updating DA for over a year. But out of the blue, it updated itself recently, and the letsencrypt script was as well updated, breaking the functionality. I have switched to paid certificates now. And downgrading DA? I am not sure if I want to ever try that on CentOS 6.