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.

This is no substitute for a proper tutorial, but rather a MaNGOS biased supplement to one.

The first thing you do should be configure a real name and email. By default, Git chooses a default name based on the GECOS data (which is probably right) and a default email based on your login and hostname (which is almost certainly wrong).

Best practices dictate you use your real name and email here, not your login, IRC handle, or any other aliases you may have.

These fields will be immortalized in the repository history so make sure you get them right.

$ git config --global user.name "Your Name" 
$ git config --global user.email "Your@emailAddress" 

While you’re configuring, you may want to enable colouring for some commands:

$ git config --global color.diff auto 
$ git config --global color.status auto 
$ git config --global color.branch auto 
$ git config --global color.interactive auto 

While Git will accept just about any commit message you feed to it, sticking to best practices makes the log a lot easier to work with.

A model commit message is shown below.

Short (50 chars or less) summary of changes

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body. The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.

Further paragraphs come after blank lines.

 - Bullet points are okay, too
 - Typically a hyphen or asterisk is used for the bullet, preceded by a
 single space, with blank lines in between, but conventions vary here.
 - Use a hanging indent

As far as submitting your work to the MaNGOS core, the work flow here is still being fleshed out. For now, either give a public URL and branch where your contribution can be found, or use the following series of commands to get a file that can be easily applied by anyone with the git am command to reconstruct your history locally.
 

$ git checkout my_funky_branch 
$ git rebase origin/master 
$ git format-patch --stdout origin/master.. > my_funky_patches 

Here’s a tip for keeping up to date: In lieu of using git pull to download the latest changes, use:

$ git pull –rebase --recurse-submodules 

Instead of cluttering the history with a merge commit, it reapplies your changes to the latest upstream.

The only caveat is that you shouldn’t use this method if you’ve already published the changes to another repository. Doing so would cause problems for anyone who has already downloaded the original commits.

As you may have noticed, from time to time there is a news article on the left side of the login screen for the WoW Client. Sometimes it can be annoying having a Blizzard notice that the servers are going down, when in reality, your server(s) is not going to be going down for maintenance in the foreseeable future.

Here are instructions on how to alleviate this problem for you and your players, should you have anyone else on your server:

Disabling Breaking News

First, we need to go into our “hosts” file, which, depending on your operating system, will be in a different location. For Windows, the hosts file is in C:\Windows\System32\drivers\etc\hosts. In order to edit this file, though, you are going to have to go into your start menu, type notepad, right-click on notepad and run as administrator. Then just hit file, open, and navigate to the hosts file. For *NIX, the location of the “hosts” file is /etc/hosts.

Second, once you are editing the “hosts” file, you will need to go to the end of the file and enter the ip address of your server, in my case it would be 192.168.0.4. Then tab over to the space under “localhost” and enter the actual servername of the warcraft breaking news server, again, in my case it was “launcher.worldofwarcraft.com”. Depending on your region the address will be different. There will be a list of breaking news server later.

Finally, once you are done modifying your “hosts” file, you can restart the client and you will never see Blizzard’s breaking news again.

“Pushing” Breaking News for your Server

In order to start “pushing” your own news, follow the instructions from Disabling Breaking News and then, once you have finished modifying your “hosts” file, come back to this section. I’m assuming that you are using the WAMP server which covers both MySQL and Apache and are on Windows. If you are in *NIX, then you should not have to worry about MySQL and Apache as they should both already be installed, normally.

With our server configuration out of the way, we are ready to begin preparing to push our own news to our clients.

In the root web directory for your domain name or ip address, create a file called “Alert”. No quotation marks, no file extension, just Alert. And yes, capitalize the A. Alert is an over-simplified html file. As an example Alert file we have:

SERVERALERT:<html><body><p>Your Message.</p></body></html>

If you feel the need to disable your news system again at a future date, simply rename Alert to something like Alert2. When you want to re-enable your news system for a new tidbit of news, all you have to do is move Alert2 back to Alert and edit it.

Blizzard’s Breaking News Servers

US/SEA - http://launcher.worldofwarcraft.com/alert

LA - http://launcher.worldofwarcraft.com/es/alert

EN - http://status.wow-europe.com/en/alert

ES - http://status.wow-europe.com/es/alert

FR - http://status.wow-europe.com/fr/alert

DE - http://status.wow-europe.com/de/alert

RU - http://status.wow-europe.com/ru/alert

KR - ??? http://launcher.worldofwarcraft.co.kr/alert

CN - ??? http://launcher.battlenet.com.cn/alert

TW - ??? http://launcher.wowtaiwan.com.tw/alert

We need to create an account to use with the server.

account create testuser mypassword

This will set up a user called testuser with a password of mypassword

In order to use the expansions

for Classic -

No need to do anything

for TBC -

account set addon testuser 1

for WotLK -

account set addon testuser 2

for Cata -

account set addon testuser 3

for Mop -

account set addon testuser 4

Setting up the client to access the server

1) Navigate to the location of the Warcraft Client installed on your local PC

2) Navigate to the “Data\enGB” folder (or other locale if not uk)
- On Classic this file is in the root folder, so you don't need to do this.
- On Mop the realmlist.wtf is merged with config.wtf in the WTF folder.

3) Open the file “realmlist.wtf” with WordPad

It will contain the following lines (actual detail may vary slightly) :-

set realmlist eu.logon.worldofwarcraft.com
set patchlist enGB.patch.battle.net:1119/patch 

Change these values to the IP address of the server.

That’s it. You are ready to roll....

Before continuing, please consider taking steps to secure your server such as disabling remote root access to your shell and database, disable remote access for your mangos database user, change your router password to something strong, install any firmware updates for your router and any security updates available for your server. Unless you are comfortable with the risk and know how to protect yourself, be careful of who you share your server information with.

 OK! Now that's out of the way...

These instructions are for setting up a dedicated hardware server on a home network. I didn't find clear concise instructions for setting it up for external connections so I'll share what worked for me.

These instructions assume that your server is up and running with localhost or 127.0.0.1 in the BindIP conf fields and the address column of your server's realmlist entry in your realmd (by default) schema.

Before we start...

If your server is running, stop both server and realm executables by whatever your preferred method is.

Server Conf

Use the ip a command to determine your server's LAN IP address. Probably something like 192.168.1.xxx.

In both your mangosd.conf and realmd.conf change the BindIP value to a string containing your server's LAN IP, like:
 

BindIP = "192.168.1.19" # or whatever the IP address might be...

Save and close both of those files.

Determine Your Server's Public IP

You will need your public IP address which you can find by googling "what is my public ip address". IMPORTANT: Make sure that you do this from the server itself. Jot that down.

DB

Now open MySQL Workbench or the MySQL shell or whatever your favorite means of SQL delivery.

In the realmd schema (by default) in the realmlist table find the entry for your server.

Update the address column to be your public IP address that you jotted down before and in the localAddress column, put your LAN IP address, like 192.168.1.xxx.

Port Forwarding

If you have a netgear router you will go to routerlogin.net. You need to login with your admin username and password. The username is probably admin unless you changed it. The password is either in your router's documentation (on a card or something), on a sticker on the router or it's something you changed it to. That's on you.

If these next instructions don't work for you, you may need to poke around your router's proprietary UI to find the right options... Good luck!

• At the top choose the ADVANCED tab.
• On the left, choose Advanced Setup
• On the Advanced Setup submenu, choose  Port Forwarding / Port Triggering
• You will need to create 3 forwarding rules.
• For each PortNumber of the ports 3443, 3724 and 8085:
  • Click the +Add Custom Service button
  • Fill in the service name with something, maybe "mangosX"
  • In the External Starting Port field, put the PortNumber
  • In the External Ending Port field, put the PortNumber
  • In the Internal IP address field, put your server's LAN IP address, 192.168.1... (probably)
  • Click the Apply button to save the rule

Now you can start your server back up by your preferred method.

There's just one more step and that's setting up our client's realmlist.wtf file. This is also the part you'll tell your friends when they want to connect.

Over wherever your actual WoW client lives, find the realmlist.wtf file and change the IP to the external IP address that you just jotted down previously.

In your realmlist.wtf file you should now have:

set realmlist <whateverYourExternalIPAddressIs>
set patchlist <whateverYourExternalIPAddressIs>

You (or your friend) is now ready to start their client with Wow.exe and join your awesome cool publicly available server! Enjoy!