All about Git - official page

Some good video talks about http:

• Linus Torvalds: History&Concepts
• Scott Chacon: Git basics, live examples
• Randal Schwartz: Git basics, descriptional
• Jesica Kerr: Git basics, descriptional

A good book of the subject:

• Pro-Git

Install Git

On Windows

Install MySysGit (Be sure to check the install with "Git bash here" support)

On Linux

Use your package manager to install git.

Basic Functions

Cloning a repo to your hard drive

The most basic form of this command is:

$ git clone --recursive http://github.com/{username}/{reponame}

A slightly better form is to specify the folder name of the local repo:

$ git clone --recursive http://github.com/{username}/{reponame} {localreponame}

In the case of mangosZero this would be a valid command to clone it correctly to a folder called 0server

$ git clone --recursive http://github.com/mangoszero/server serverZero

Sometimes you may want to clone a specific branch i.e. develop21

$ git clone --recursive http://github.com/{username}/{reponame} -b develop21 {localreponame}

Updating an existing repo with the latest source

From the folder containing the source, type:

$ git pull --recurse-submodules

This will pull in all updated files, you can then proceed to build using Visual Studio or cmake/make on Linux.

Original credit @H0zen rewritten in part by myself.

Our covenant servers hold lots of user and character data, we need to make sure that is safe and one of the tasks we do is multiple daily backups to an offsite FTP server.

This script is ran via cronjob and can be ran as many times a day as you like. You will need to run things like "yum install ftp" for the ftp part and have zip installed.

Make sure you change the parts suck as yourbackupfilename, servername, MySQL/FTP details, the password on the zip file and the folder path "remotefolder" in the FTP transfer section.

#!/bin/sh

# Archive & file variables
ARCHIVE=yourbackupfilename`date +"%F"`
OLDARCHIVE=yourbackupfilename-`date --date '-5 days' +"%F"`
FILE=servername-Realmd_`date +"%F"`
FILE0=servername-ZERO-Chars_`date +"%F"`
FILE1=servername-ONE-Chars_`date +"%F"`
FILE2=servername-TWO-Chars_`date +"%F"`

# MySQL variables
DBSERVER=127.0.0.1
REALMD_DATABASE=realmd
CHARACTERSS_ZERO_DATABASE=characters-classic_servername
CHARACTERSS_ONE_DATABASE=characters-tbc_servername
CHARACTERSS_TWO_DATABASE=characters-wotlk_servername
USER=rootuser
PASS=rootpassword

# FTP transfer on demand connection & login details
FTP_USER=ftpuser
FTP_PASS=ftppass
FTP_HOST=ftphostname

# Remove previous .zip files if multiple daily backups are being ran
echo "Checking and removing as needed old .zip files locally."
rm -f $ARCHIVE.zip
rm -f $OLDARCHIVE.zip

# Dump MySQL database in .sql files into /root
echo "Dumping .sql files to /root"
mysqldump --opt --user=${USER} --password=${PASS} ${REALMD_DATABASE} > ${FILE}.sql
mysqldump --opt --user=${USER} --password=${PASS} ${CHARACTERSS_ZERO_DATABASE} > ${FILE0}.sql
mysqldump --opt --user=${USER} --password=${PASS} ${CHARACTERSS_ONE_DATABASE} > ${FILE1}.sql
mysqldump --opt --user=${USER} --password=${PASS} ${CHARACTERSS_TWO_DATABASE} > ${FILE2}.sql
echo ".sql files have been dumped to /root."

# Zip dumped MySQL .sql files and password the zip file
echo "Zipping dumped .sql files."
zip -e -P backupfilepassword $ARCHIVE.zip $FILE.sql $FILE0.sql ${FILE1}.sql ${FILE2}.sql

# Show the user the result
echo "${ARCHIVE}.zip was created!"

# Move the file via ftp to remote NAS
echo "Initiating FTP transfer on demand."
ftp -n $FTP_HOST <<END_SCRIPT
quote USER $FTP_USER
quote PASS $FTP_PASS
cd remotefolder/remotefolder
binary
delete $OLDARCHIVE.zip
put $ARCHIVE.zip
quit
END_SCRIPT
# FTP transfer on demand ends

# Tidy up files in the /root folder
rm -f /root/*.sql
echo "Clearing dumped local .sql files."

Mangos Backup Cron Script.txt

Description of the 'account' table.

This table holds information on all available accounts.

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

id int(11) unsigned

The unique account ID.

username varchar(32)

The account user name.

sha_pass_hash varchar(40)

This field contains the encrypted password. The encryption is SHA1 and is in the following format: username:password. The SQL to create the password (or to compare with the current hash) is:

SELECT SHA1(CONCAT(UPPER(`username`), ':', UPPER({pass})));

gmlevel tinyint(3) unsigned

The account security level. Different levels have access to different commands. The individual level required for a command is defined in the Mangos command table. Valid values are:

Value	Description
0	Player
1	Moderator
2	Gamemaster
3	Administrator
4	Access control within the world server console only

sessionkey longtext

The SessionKey - this is the validated result of the login negotiation. This allows disconnected clients to reconnection to their previous session.

v longtext

The validated Hash Value, this is created by using the 'Salt' value [See account.s] applied to the username/password SHA1 hash (See account.sha_pass_hash).

s longtext

Password 'Salt' Value. Initially a randomly generated value, which when applied against the SHA1 hash of the username / password combo [See account.sha_pass_hash] produces the validation hash (See account.v).

email text

The e-mail address associated with this account.

joindate timestamp

The date when the account was created.

last_ip varchar(30)

The last IP used by the person who last logged into the account.

failed_logins int(11) unsigned

The number of failed logins attempted on the account. Monitoring this field may help spotting users who try to gain access to accounts which are not their own, or who have forgotten their passwords.

locked tinyint(3) unsigned

Boolean 0 or 1 controlling if the account has been locked or not.

last_login timestamp

The date when the account was last logged into.

active_realm_id int(11) unsigned

This Field contains the RealmId of the last realm that the account was used on.

expansion tinyint(3) unsigned

The field controls to which expansion's content a user has access. By default this is set to 0, allowing access to vanilla WoW content. In mangos-zero, other values can be ignored, since there is no expansion.

Value	Expansion
0	World of Warcraft *
1	Burning Crusade
2	Wrath of the Lich King
3	Cataclysm
4	Mists of Pandaria
5	Warlords of Draenor
6	Legion
7	Battle for Azeroth

* Base Game Version of World of Warcraft, otherwise known as Vanilla. The world server will block access to accounts with 0 in this field from accessing the TBC and WotLK areas in-game. The world server will block access to accounts with 1 in this field from accessing the WotLK areas in-game and so on.

mutetime bigint(40) unsigned

The time, in Unix time, when the account will be unmuted.

SELECT `username`, FROM_UNIXTIME(`mutetime`) FROM `account`;

locale tinyint(3) unsigned

The locale used by the client logged into this account. If multiple locale data has been configured and added to the world servers, the world servers will return the proper locale strings to the client.

Value	Language
0	English
1	Korean
2	French
3	German
4	Chinese
5	Taiwanese
6	Spanish Spain
7	Spanish Latin America
8	Russian

os varchar(3)

The Operating System of the connected client. This is used by the Warden Module

playerBot bit(1)

Determines whether the account is a User or a PlayerBot.

Value	Account Type
0	Normal User
1	Playerbot account

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'account_banned' table.

This table lists all of the accounts that have been banned along with the date when (or if) the ban will expire.

Table Notes

This table uses the 'MyISAM' DB Engine

The Field definitions follow:

Description of the fields

id int(11) unsigned

The account ID [See account.id].

bandate bigint(40)

The date when the account was banned, in Unix time.

unbandate bigint(40)

The date when the account will be automatically unbanned, in Unix time. A value less than the current date means, in effect, a permanent ban.

bannedby varchar(50)

The character with the rights to the .ban command that banned the account.

banreason varchar(255)

The reason for the ban.

active tinyint(4)

This is a Boolean field controlling if the ban is currently active or not.

auto-generated by the getMaNGOS.eu MAGNET dbdocs module

Description of the 'account_data' table for MaNGOSThree

Table Notes

This table uses the 'InnoDB' DB Engine

The Field definitions follow:

Description of the fields

account int(11) unsigned

type int(11) unsigned

time bigint(11) unsigned

data longblob

auto-generated by the getMaNGOS.eu MAGNET dbdocs module