Main difference: if you have a shell and you have root privileges you can do pretty much whatever you fancy!
Just an admin webpanel is (usually) much more restrictive. I won't get into php shells...

If you have command line access and appropriate privileges then if every step of updating is known to you AND you know how to check that nothing is broken you could use the following setup:

-write a script that checks for updates, put it into the user running the website's cron.

-either install updates directly then have the script email you the result of the tests (quite simple, those would just be akin to "try and retrieve this webpage, click on that link, login as this name)

-or keep a vm running on the server where the site is hosted, said vm would be a mirror of the site but only reachable from the server itself (ssh tunelling of http would allow you to consult it from your browser) this vm would get all the updates before the main site would that way if any update breaks something then you'll be aware of it. Once it's installed on the vm I reckon it'd be trivial to update the main website (either downloading the updates from the vm or directly from the update servers).

This is disturbing,  is it a result of the break in? Updating should not change the database content so neither your credentials nor anyone else's should change.  To be sure you should keep a full backup (website and database) handy.   first you have to determine what database the forum is using (you should find this information in either yabb documentation or in your cms configuration files) if you want to make a backup.

If you ever decide to completely rewrite the site you'd still be able to use the same database mind you.

What I'm trying to say here is that the update should boil down to changing existing files and/or creating new ones. Those things are easy to automate  since they are easy to do from the command line.  What you can do is:

-jot down every step of updating (such as navigate to t this.url download from this link, unzip in this location)

-write all the commands in a file.  Make it executable

-crontab -e  and add the newly created program  so it runs at regular intervals.

If like me you have issues with bash syntax then I'd advise using perl (or python  or ruby).

English is not my first language so if I fail at getting my point across please tell me so I can reword/clarify and learn more in the process.

Well, that's an impressive skill. During my internship I had to do some ram swapping on a server (to find a couple that would actually work) I was so worried I'd break something I could not help but feel relieved once I closed the case. And don't get me started on setting up a CPU on a motherboard. Things might have changed but I still have that (semi)irrational fear of breaking the legs of such a costly item. Or simply fry it while pulling it out of the anti static bag...

On the topic of writing scripts if you can use the command line you can write scripts thing is bash scripts can be really hard to understand. That's why I started using perl and never looked back. If you can't be bothered with the learning curve you can have a look at python (there are more projects on raspberry pi using python than you can shake a stick at, and those can be a real fun way to learn. Desktop trebuchet anyone?).

Since you already have some experience at website administration you already qualify as a power user and should be able to avoid the most obvious snags while getting started with a scripting language. There also are some great communities out there with many helpful members. These days you can't throw a rock without hitting a couple of pythonista so if you're having a hard time you'll always have someone to ask for help.

Sorry if that sound like proselytism... Ok I might be trying to convert you, is it that obvious?

lol
lost count of the number of cpu pins I've had to straighten over the years. Mostly they get bent when you take them out in a hurry.

I do have a raspberry pi model b. Alas it won't display a picture on any of my workshop monitors - even got an hdmi to vga adaptor - that doesn't work either.

So that's still in the box lol

Given how many projects you can make with one and a 3d printer I really ought to try again.
Got a newer monitor in the corner that might work.
thing is my workshop monitors are always things that people were about to throw away

I will make an effort to get the website back up.

I'm actually going to get a bbc mini computer thing. Was hoping david morningstar - who was/is on the development team might be able to 'borrow' one for me. But alas no.

It's seriously tiny, will run on a 3 volt coincell and has a built in accelerometer. I want to make a sling pouch it fits in so I can actually measure the pouch speed on release.

It will talk wirelessly to an android tablet (I think).

It's on The List, lol

I think it would stay in the pouch but correct me if I'm wrong.

im not able to view the member map or the hall of fame section