Change most http links to https

docs/source/Coding/Coding-Introduction.md

@@ -20,7 +20,7 @@ take a look at our [Python introduction](../Howto/Starting/Part1/Python-basic-in
 
 When new to Evennia it can be hard to find things or figure out what is available. Evennia offers a
 special interactive python shell that allows you to experiment and try out things. It's recommended
-to use [ipython](http://ipython.org/) for this since the vanilla python prompt is very limited. Here
+to use [ipython](https://ipython.org/) for this since the vanilla python prompt is very limited. Here
 are some simple commands to get started:
 
     # [open a new console/terminal]
@@ -84,7 +84,7 @@ should just gracefully tell you what errors it finds, it can nevertheless be a g
 check your code for simple syntax errors *before* you load it into the running server.  There are
 many python syntax checkers out there. A fast and easy one is
 [pyflakes](https://pypi.python.org/pypi/pyflakes), a more verbose one is
-[pylint](http://www.pylint.org/). You can also check so that your code looks up to snuff using
+[pylint](https://www.pylint.org/). You can also check so that your code looks up to snuff using
 [pep8](https://pypi.python.org/pypi/pep8). Even with a syntax checker you will not be able to catch
 every possible problem - some bugs or problems will only appear when you actually run the code. But
 using such a checker can be a good start to weed out the simple problems.
@@ -131,7 +131,7 @@ call, but reading docs really *does* help you, promise! Evennia's documentation
 and knowing what is possible can often give you a lot of new cool game ideas. That said, if you
 can't find the answer in the docs, don't be shy to ask questions! The [discussion
 group](https://sites.google.com/site/evenniaserver/discussions) and the [irc
-chat](http://webchat.freenode.net/?channels=evennia) are also there for you.
+chat](https://webchat.freenode.net/?channels=evennia) are also there for you.
 
 ### The most important point
 

docs/source/Coding/Unit-Testing.md

@@ -4,7 +4,7 @@
 *Unit testing* means testing components of a program in isolation from each other to make sure every
 part works on its own before using it with others. Extensive testing helps avoid new updates causing
 unexpected side effects as well as alleviates general code rot (a more comprehensive wikipedia
-article on unit testing can be found [here](http://en.wikipedia.org/wiki/Unit_test)).
+article on unit testing can be found [here](https://en.wikipedia.org/wiki/Unit_test)).
 
 A typical unit test set calls some function or method with a given input, looks at the result and
 makes sure that this result looks as expected. Rather than having lots of stand-alone test programs,
@@ -99,7 +99,7 @@ Example of a `TestCase` class:
 ```
 
 You might also want to read the [documentation for the unittest
-module](http://docs.python.org/library/unittest.html).
+module](https://docs.python.org/library/unittest.html).
 
 ### Using the EvenniaTest class
 

docs/source/Coding/Updating-Your-Game.md

@@ -8,7 +8,7 @@ the [Getting Started guide](../Setup/Setup-Quickstart) and get everything runnin
 
 Very commonly we make changes to the Evennia code to improve things. There are many ways to get told
 when to update: You can subscribe to the RSS feed or manually check up on the feeds from
-http://www.evennia.com. You can also simply fetch the latest regularly.
+https://www.evennia.com. You can also simply fetch the latest regularly.
 
 When you're wanting to apply updates, simply `cd` to your cloned `evennia` root directory and type:
 
@@ -131,4 +131,4 @@ automatically for you. Basically, whenever the schema changes we distribute smal
 "migrations" with the source. Those tell the system exactly how to implement the change so you don't
 have to do so manually. When a migration has been added we will tell you so on Evennia's mailing
 lists and in commit messages -
-you then just run `evennia migrate` to be up-to-date again. 
+you then just run `evennia migrate` to be up-to-date again. 

docs/source/Coding/Using-Travis.md

@@ -1,9 +1,9 @@
 # Using Travis
 
-Evennia uses [Travis CI](http://travis-ci.org/) to check that it's building successfully after every
+Evennia uses [Travis CI](https://travis-ci.org/) to check that it's building successfully after every
 commit to its Github repository (you can for example see the `build: passing` badge at the top of
 Evennia's [Readme file](https://github.com/evennia/evennia)). If your game is open source on Github
-you may also use Travis for free. See [the Travis docs](http://docs.travis-ci.com/user/getting-
+you may also use Travis for free. See [the Travis docs](https://docs.travis-ci.com/user/getting-
 started/) for how to get started.
 
 After logging in you will get to point Travis to your repository on github. One further thing you
@@ -34,4 +34,4 @@ will be able to see it.
 
 For properly testing your game you of course also need to write unittests. [We have a page](Unit-
 Testing) on how we set those up for Evennia, you should be able to refer to that for making tests
-fitting your game.
+fitting your game.

docs/source/Coding/Version-Control.md

@@ -6,7 +6,7 @@ able to easily backtrack these changes, share your development efforts and more.
 contributing to Evennia itself, and only wish to develop your own MU* using Evennia, having a
 version control system in place is a good idea (and standard coding practice). For an introduction
 to the concept, start with the Wikipedia article
-[here](http://en.wikipedia.org/wiki/Version_control). Evennia uses the version control system
+[here](https://en.wikipedia.org/wiki/Version_control). Evennia uses the version control system
 [Git](https://git-scm.com/) and this is what will be covered henceforth. Note that this page also
 deals with commands for Linux operating systems, and the steps below may vary for other systems,
 however where possible links will be provided for alternative instructions.
@@ -18,7 +18,7 @@ documentation](https://help.github.com/articles/set-up-git#platform-all).
 
 If you have gotten Evennia installed, you will have Git already and can skip to **Step 2** below.
 Otherwise you will need to install Git on your platform. You can find expanded instructions for
-installation [here](http://git-scm.com/book/en/Getting-Started-Installing-Git).
+installation [here](https://git-scm.com/book/en/Getting-Started-Installing-Git).
 
 ### Step 1: Install Git
 
@@ -30,9 +30,9 @@ installation [here](http://git-scm.com/book/en/Getting-Started-Installing-Git).
 
         apt-get install git    
 
-- **Windows**: It is recommended to use [Git for Windows](http://msysgit.github.io/). 
+- **Windows**: It is recommended to use [Git for Windows](https://gitforwindows.org/). 
 - **Mac**:  Mac platforms offer two methods for installation, one via MacPorts, which you can find
-out about [here](http://git-scm.com/book/en/Getting-Started-Installing-Git#Installing-on-Mac), or
+out about [here](https://git-scm.com/book/en/Getting-Started-Installing-Git#Installing-on-Mac), or
 you can use the [Git OSX Installer](https://sourceforge.net/projects/git-osx-installer/).
  
 ### Step 2: Define user/e-mail Settings for Git
@@ -282,7 +282,7 @@ git merge master
 If everything went well, your `myfixes` branch will now have the latest version of Evennia merged
 with whatever changes you have done.  Use `git log` to see what has changed. You may need to restart
 the server or run `manage.py migrate` if the database schema changed (this will be seen in the
-commit log and on the mailing list). See the [Git manuals](http://git-scm.com/documentation) for
+commit log and on the mailing list). See the [Git manuals](https://git-scm.com/documentation) for
 learning more about useful day-to-day commands, and special situations such as dealing with merge
 collisions.
 
@@ -472,4 +472,4 @@ git config --global alias.grep 'grep -Ii'
 To get a further feel for GIT there is also [a good YouTube talk about
 it](https://www.youtube.com/watch?v=1ffBJ4sVUb4#t=1m58s) - it's a bit long but it will help you
 understand the underlying ideas behind GIT
-(which in turn makes it a lot more intuitive to use).
+(which in turn makes it a lot more intuitive to use).