Mogdar,
You wouldn't happen to be from Guardians of the Keep on Drinal, would you? It was many years ago, but one of our original officers back in the day had the same name (Mogdar).
Anyway, as mentioned, your update process may differ depending on the type of server you want to run.
You will need to pay attention to the changelog.txt file that comes with the source code, and make sure that you follow any of the required changes in there if you update your source code. You can get by without updating your DB regularly, as long as you are doing the required SQL updates that come with source code updates.
It isn't required to update regularly unless you want to. Most of the time, people update when a feature or content comes out that is significant enough to warrant an update of their server. You can't really fully automate the process, since both DB and Source Code rely on each other being at the same version. If changes are made related to new DB fields and your DB and Source Code don't both include that particular change, then something will definitely be broken on your server. So, you can't just set your server to update the DB automatically every day. The update process could probably be automated for most updates, but every now and then a major change comes along that requires manual intervention.
My recommendation would be for you to update your server maybe once per month or as time permits. Most likely, there aren't going to be regular massive updates that would warrant updating your server more frequently than that.
|