Update all links to use https (#2120)

Author: Arhell

.editorconfig

@@ -1,5 +1,5 @@
 ; This file is for unifying the coding style for different editors and IDEs.
-; More information at http://editorconfig.org
+; More information at https://editorconfig.org
 
 root = true
 

.gitattributes

@@ -2,7 +2,7 @@
 * text text=auto eol=lf
 
 # These files are always considered text and should use LF.
-# See core.whitespace @ http://git-scm.com/docs/git-config for whitespace flags.
+# See core.whitespace @ https://git-scm.com/docs/git-config for whitespace flags.
 *.php   text eol=lf whitespace=blank-at-eol,blank-at-eof,space-before-tab,tab-in-indent,tabwidth=4 diff=php
 *.json  text eol=lf whitespace=blank-at-eol,blank-at-eof,space-before-tab,tab-in-indent,tabwidth=4
 *.test  text eol=lf whitespace=blank-at-eol,blank-at-eof,space-before-tab,tab-in-indent,tabwidth=4

CONTRIBUTING.md

@@ -91,5 +91,5 @@ install [docker-compose](https://docs.docker.com/compose/) for your platform.
 
 ## Documentation
 
-The Phinx documentation is stored in the **docs** directory using the [RestructedText](http://docutils.sourceforge.net/rst.html)
+The Phinx documentation is stored in the **docs** directory using the [RestructedText](https://docutils.sourceforge.io/rst.html)
 format. All documentation merged to `master` is automatically published to the Phinx documentation site available at http://docs.phinx.org.

docs/en/configuration.rst

@@ -335,10 +335,10 @@ Supported Adapters
 
 Phinx currently supports the following database adapters natively:
 
-* `MySQL <http://www.mysql.com/>`_: specify the ``mysql`` adapter.
-* `PostgreSQL <http://www.postgresql.org/>`_: specify the ``pgsql`` adapter.
-* `SQLite <http://www.sqlite.org/>`_: specify the ``sqlite`` adapter.
-* `SQL Server <http://www.microsoft.com/sqlserver>`_: specify the ``sqlsrv`` adapter.
+* `MySQL <https://www.mysql.com/>`_: specify the ``mysql`` adapter.
+* `PostgreSQL <https://www.postgresql.org/>`_: specify the ``pgsql`` adapter.
+* `SQLite <https://www.sqlite.org/>`_: specify the ``sqlite`` adapter.
+* `SQL Server <https://www.microsoft.com/sqlserver>`_: specify the ``sqlsrv`` adapter.
 
 For each adapter, you may configure the behavior of the underlying PDO object by setting in your
 config object the lowercase version of the constant name. This works for both PDO options

docs/en/migrations.rst

@@ -172,7 +172,7 @@ Executing Queries
 Queries can be executed with the ``execute()`` and ``query()`` methods. The
 ``execute()`` method returns the number of affected rows whereas the
 ``query()`` method returns the result as a
-`PDOStatement <http://php.net/manual/en/class.pdostatement.php>`_. Both methods
+`PDOStatement <https://php.net/manual/en/class.pdostatement.php>`_. Both methods
 accept an optional second parameter ``$params`` which is an array of elements,
 and if used will cause the underlying connection to use a prepared statement.
 
@@ -237,7 +237,7 @@ and if used will cause the underlying connection to use a prepared statement.
     If Phinx was to iterate any potential result sets, looking to see if one
     had an error, then Phinx would be denying access to all the results as there
     is no facility in PDO to get a previous result set
-    `nextRowset() <http://php.net/manual/en/pdostatement.nextrowset.php>`_ -
+    `nextRowset() <https://php.net/manual/en/pdostatement.nextrowset.php>`_ -
     but no ``previousSet()``).
 
     So, as a consequence, due to the design decision in PDO to not throw
@@ -246,8 +246,8 @@ and if used will cause the underlying connection to use a prepared statement.
 
     Fortunately though, all the features of PDO are available, so multiple batches
     can be controlled within the migration by calling upon
-    `nextRowset() <http://php.net/manual/en/pdostatement.nextrowset.php>`_
-    and examining `errorInfo <http://php.net/manual/en/pdostatement.errorinfo.php>`_.
+    `nextRowset() <https://php.net/manual/en/pdostatement.nextrowset.php>`_
+    and examining `errorInfo <https://php.net/manual/en/pdostatement.errorinfo.php>`_.
 
 Fetching Rows
 -------------

docs/en/namespaces.rst

@@ -90,15 +90,15 @@ Let's take a closer look on how the paths are resolved, let's start with the non
 This is the directory where Phinx will look for migrations when migrating.
 NB. these migrations must not have a namespace.
 
-.. image:: http://i.imgur.com/l84308Q.jpg
+.. image:: https://i.imgur.com/l84308Q.jpg
 
 This image shows the path for "./db/migrations" where "Phinx" is the project root.
 
 And the namespaced path would be resolved as shown below.
 
 "./src/FooBar/db/migrations" would resolve to <project-root>/src/FooBar/db/migrations, which is where Phinx will look for migrations in the Foo\\Bar namespace.
 
-.. image:: http://i.imgur.com/2mg0V8V.jpg
+.. image:: https://i.imgur.com/2mg0V8V.jpg
 
 The file path would look like this, if the project-root was "Phinx"
 

docs/fr/configuration.rst

@@ -241,10 +241,10 @@ Supported Adapters
 
 Phinx currently supports the following database adapters natively:
 
-* `MySQL <http://www.mysql.com/>`_: specify the ``mysql`` adapter.
-* `PostgreSQL <http://www.postgresql.org/>`_: specify the ``pgsql`` adapter.
-* `SQLite <http://www.sqlite.org/>`_: specify the ``sqlite`` adapter.
-* `SQL Server <http://www.microsoft.com/sqlserver>`_: specify the ``sqlsrv`` adapter.
+* `MySQL <https://www.mysql.com/>`_: specify the ``mysql`` adapter.
+* `PostgreSQL <https://www.postgresql.org/>`_: specify the ``pgsql`` adapter.
+* `SQLite <https://www.sqlite.org/>`_: specify the ``sqlite`` adapter.
+* `SQL Server <https://www.microsoft.com/sqlserver>`_: specify the ``sqlsrv`` adapter.
 
 SQLite
 ~~~~~~

docs/fr/migrations.rst

@@ -161,7 +161,7 @@ Executing Queries
 Queries can be executed with the ``execute()`` and ``query()`` methods. The
 ``execute()`` method returns the number of affected rows whereas the
 ``query()`` method returns the result as a
-`PDOStatement <http://php.net/manual/en/class.pdostatement.php>`_::
+`PDOStatement <https://php.net/manual/en/class.pdostatement.php>`_::
 
     <?php
 
@@ -211,7 +211,7 @@ Queries can be executed with the ``execute()`` and ``query()`` methods. The
     If Phinx was to iterate any potential result sets, looking to see if one
     had an error, then Phinx would be denying access to all the results as there
     is no facility in PDO to get a previous result set
-    `nextRowset() <http://php.net/manual/en/pdostatement.nextrowset.php>`_ -
+    `nextRowset() <https://php.net/manual/en/pdostatement.nextrowset.php>`_ -
     but no ``previousSet()``).
 
     So, as a consequence, due to the design decision in PDO to not throw
@@ -220,8 +220,8 @@ Queries can be executed with the ``execute()`` and ``query()`` methods. The
 
     Fortunately though, all the features of PDO are available, so multiple batches
     can be controlled within the migration by calling upon
-    `nextRowset() <http://php.net/manual/en/pdostatement.nextrowset.php>`_
-    and examining `errorInfo <http://php.net/manual/en/pdostatement.errorinfo.php>`_.
+    `nextRowset() <https://php.net/manual/en/pdostatement.nextrowset.php>`_
+    and examining `errorInfo <https://php.net/manual/en/pdostatement.errorinfo.php>`_.
 
 Fetching Rows
 -------------

docs/ja/configuration.rst

@@ -236,10 +236,10 @@ Phinx は ``PHINX_`` というプレフィックスが付いた環境変数を
 
 Phinx は現在、次のデータベースアダプターをネイティブにサポートしています。
 
-* `MySQL <http://www.mysql.com/>`_: ``mysql`` アダプターを指定。
-* `PostgreSQL <http://www.postgresql.org/>`_: ``pgsql`` アダプターを指定。
-* `SQLite <http://www.sqlite.org/>`_: ``sqlite`` アダプターを指定。
-* `SQL Server <http://www.microsoft.com/sqlserver>`_: ``sqlsrv`` アダプターを指定。
+* `MySQL <https://www.mysql.com/>`_: ``mysql`` アダプターを指定。
+* `PostgreSQL <https://www.postgresql.org/>`_: ``pgsql`` アダプターを指定。
+* `SQLite <https://www.sqlite.org/>`_: ``sqlite`` アダプターを指定。
+* `SQL Server <https://www.microsoft.com/sqlserver>`_: ``sqlsrv`` アダプターを指定。
 
 SQLite
 ~~~~~~

docs/ja/migrations.rst

@@ -159,7 +159,7 @@ up メソッドで記述された変換を元に戻すには、down メソッド
 
 クエリーは、 ``execute()`` と ``query()`` メソッドで実行できます。
 ``execute()`` メソッドは影響を受ける行の数を返しますが、 ``query()`` メソッドは結果を
-`PDOStatement <http://php.net/manual/ja/class.pdostatement.php>`_
+`PDOStatement <https://php.net/manual/ja/class.pdostatement.php>`_
 として返します。 ::
 
     <?php
@@ -208,14 +208,14 @@ up メソッドで記述された変換を元に戻すには、down メソッド
     Phinx が潜在的な結果セットを反復して、１つのエラーがあることを発見した場合、
     以前の結果セットを得る機能が PDO にはないため、Phinx はすべての結果へのアクセスを拒否します。
     (``previousSet()`` ではなく
-    `nextRowset() <http://php.net/manual/ja/pdostatement.nextrowset.php>`_) 。
+    `nextRowset() <https://php.net/manual/ja/pdostatement.nextrowset.php>`_) 。
 
     その結果、バッチ処理されたクエリーの例外を投げないようにする PDO の設計上の決定により、
     Phinx はクエリーのバッチが提供されたときにエラー処理を最大限にサポートすることができません。
 
     幸いにも、PDO のすべての機能が利用可能であるため、
-    `nextRowset()  <http://php.net/manual/ja/pdostatement.nextrowset.php>`_
-    を呼び出して `errorInfo <http://php.net/manual/ja/pdostatement.errorinfo.php>`_
+    `nextRowset()  <https://php.net/manual/ja/pdostatement.nextrowset.php>`_
+    を呼び出して `errorInfo <https://php.net/manual/ja/pdostatement.errorinfo.php>`_
     を調べることで、複数のバッチをマイグレーション中に制御することができます。
 
 行の取得