Note: The following three posts were copied over from another thread, where they were off-topic.
Well, vBulletin does provide patch-level updates, but I don't know how far they reach. So for instance, if you're running 4.2.1, then you can patch that up to 4.2.3 and it should remain fully compatible. But what I do not know is to what extent such a patch-level update will honor any customizations you've applied to the code since the initial installation. It might overwrite everything, or it might only overwrite those parts of the code that haven't been modified.Quote:
Originally posted by Sammy
This statement is significant. As time moves forward, to be stuck on 4.1.1 could become problematic. Especially if that prevents security fix implementations. It also means a feature freeze. Maybe they have the ability to do a full rollback. That would result in the loss of the customizations but at least then they can move forward with new releases when available.Quote:
Originally posted by Aragorn
This is specific to each and every software title that gets installed outside of a package manager. vBulletin runs on GNU/Linux (or other UNIX) systems, and GNU/Linux has a package manager for installing and/or removing software ─ the package manager keeps track of every individual software package installed on the system ─ but vBulletin is third-party software that comes with its own installation procedure, outside of the package manager's scope. By consequence, the update/upgrade procedure is also specific to vBulletin itself, and so I have no idea how it works.
Oh, well, to be honest, I have so far never had to access any command-line prompt in my now four years of being the administrator of The One Truth ─ or that is to say, I have not had to use any command-line tools on the server, because I am and have already for 20+ years exclusively been running GNU/Linux on my own workstations, and I do very often use the command line here.Quote:
Originally posted by Daozen
But with regard to the management of the server, if you need to do anything specific with regard to traffic analysis, managing the server's email, managing the DNS entries, and the likes, you commonly do this by way of a web-based control panel ─ usually cPanel, but there are others, and it all depends on who your domain hosting company is. So it's all managed from within a web browser, over an encrypted connection. :)
Another thing with regard to UNIX servers ─ which includes GNU/Linux, the various BSD-based systems and OpenIndiana ─ is that once you've set up the system for a production role, almost everything is automated by way of a cron daemon of some sorts, which periodically runs scripts that do things like rotate the logs, check file integrity, index and update the file search database, et al. It really is very low-maintenance. :)
What I do recommend you would study, if you're interested in this stuff, is how to use the command line effectively, and how to write shell scripts. In GNU/Linux, the shell is most often GNU Bash, but there are others as well, such as the Z Shell, the C Shell and the Public Domain Korn Shell. They all have their specific syntax and properties, but with the exception of the C Shell, all others are pretty much compatible with the original Bourne Shell, so if you write your scripts as Bourne Shell scripts only, then they will be portable across all of those other shells.
This here is a very good starters tutorial on how to use the shell and write scripts. :)
No, that's not correct. Paul was the senior administrator at Project Avalon, and of course, he was interfacing with the server from within his own home, but that's quite common nowadays ─ I do that too. The Project Avalon server itself is however hosted at a data center.Quote:
Originally posted by Daozen
First and foremost, if you're going to be running a server out of your own home, then that's going to become incredibly costly, because you'll need a top-of-the-line internet connection with guaranteed quality-of-service, you need top-of-the-line enterprise-grade hardware (including spare parts), you need a guaranteed 24/7 uptime on account of electricity, with backup generators, you need a decent hardware firewall, et al, and the server should be placed somewhere where nobody's smoking, where there are no cats or dogs around, and where it can remain at a constant low temperature.
Data centers offer all of the above at a much smaller cost. So you hire either a virtual private server, or a dedicated server, or you supply a server of your own, and then that gets mounted into a rack in a large, air-conditioned room, with secure access, and with the hardware constantly monitored. There will also be periodic (and automated) backups, stored on an external machine. Everything is on large uninterruptible power supplies, which themselves are backed up by diesel-powered generators. You simply cannot provide for all of that inside your own home for the same amount of money.
Trust me, I've run an IRC network with a couple of other people for about seven to eight years, the last three or four years of which we were attempting to host it ourselves because we thought it would have been cheaper. Well, not so, despite all of our equipment being second-hand (but enterprise-grade). It was horribly expensive, and when stuff breaks down, you yourself have to make sure that you replace the failed components with new ones, and as soon as possible.
So the Project Avalon server actually resides in one of those specialized data centers, and so does the server of The One Truth ─ they're at different data centers, though. :)
