Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Question What is better - dist-upgrade or clean install
- Thread starter Daveo
- Start date
To me I always prefer having a clean install and migrate everything over, this way there's a fresh start of packages and not have to worry about running into any issues for an upgrade and is the method I generally use and preferred.
Now there's nothing wrong with doing a dist-upgrade but if you're going to do that make sure you have a good backup and/or snapshot because if someone goes wrong it'll go wrong fast.
But it basically comes down to what you want to do. The fast and simple method would be to do a dist-upgrade (and hope nothing breaks during the progress but let's be honest, it's Linux, the chances of something happening is pretty slim unless there's that one sneaky package that isn't supported on the newer version that throws a whole ranch in the process) while the slow progress is deploying a new server with the updated OS and doing the migration but more reliable and gives you a fresher start. Personal preferences, and everyone will have different opinions.
Now there's nothing wrong with doing a dist-upgrade but if you're going to do that make sure you have a good backup and/or snapshot because if someone goes wrong it'll go wrong fast.
But it basically comes down to what you want to do. The fast and simple method would be to do a dist-upgrade (and hope nothing breaks during the progress but let's be honest, it's Linux, the chances of something happening is pretty slim unless there's that one sneaky package that isn't supported on the newer version that throws a whole ranch in the process) while the slow progress is deploying a new server with the updated OS and doing the migration but more reliable and gives you a fresher start. Personal preferences, and everyone will have different opinions.
