• 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 Database Inbuilt Updater

matt001

New Pleskian
Hi

I am new to Plesk coming from cPanel. Within cPanel GUI when an update for MySQL was out you could use the MySQL Updater Tool within cPanel / WHM to update without having to use commands

Is their any reason why Plesk doesn't have a GUI based update tool to update MariaDB if users want to? I am no Linux Guru and would prefer if possible to do things through the GUI.

I think this would be good to have added and it allows you to choose which version you want to upgrade to to keep it up to date.

Matthew
 
I think the fact is that in Plesk, unlike the cPanel, where its value is not so important, the system database (psa) runs on the same MySQL server as the client databases. Therefore, incorrect updating of the database server can bring down the whole Plesk. Thus, this upgrade procedure is available only to CLI experienced system administrators.
 
I think the fact is that in Plesk, unlike the cPanel, where its value is not so important, the system database (psa) runs on the same MySQL server as the client databases. Therefore, incorrect updating of the database server can bring down the whole Plesk. Thus, this upgrade procedure is available only to CLI experienced system administrators.
IT experts like me :)
 
I'm completely new to webdev, having started this project only a few days ago, no Javascript experience and even no DB experience. I do have a good amount of experience in C and Python. The only webdev I had ever done was CS50 a couple of years ago, and that didn't cover much.

I've actually made a working demo version of this using a local MongoDB, a Node server and Pusher. I made the server connect to the database, listen to the changestream, and then on a change event it triggers https://speedtest.vet/ https://vidmate.bid/ the pusher event and sends the data, which is then used by the client subscribed to the pusher channel.

Now my feeling is that this is a little bit overkill. For instance, using the changestream for MongoDB required me to make a replica set, I'm sure there's a perfectly good reason for that but it seems more something for companies than for a small project like ours. In general since it's my first time I just have no idea if I should keep using this stack or change to something else.
 
Last edited:
Back
Top