[4.0.x] - Updated domain to phalcon.io

.github/ISSUE_TEMPLATE.md

@@ -1,11 +1,11 @@
-> Questions should go to https://forum.phalconphp.com
+> Questions should go to https://phalcon.link/forum
 > Documentation issues should go to https://github.com/phalcon/docs/issues
 
 ### Expected and Actual Behavior
 
 > **Describe what you are trying to achieve and what goes wrong.**
 
-> Provide output if related. Provide coredump if any. Use https://docs.phalconphp.com/en/latest/generating-backtrace as reference
+> Provide output if related. Provide coredump if any. Use https://docs.phalcon.io/latest/en/generating-backtrace as reference
 
 ```php
 // paste output here

.github/stale.yml

@@ -26,14 +26,14 @@ staleLabel: stale
 
 # Comment to post when marking as stale. Set to `false` to disable
 markComment: >
-  Thank you for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please feel free to either reopen this issue or open a new one. We will be more than happy to look at it again! You can read more here: https://blog.phalconphp.com/post/github-closing-old-issues
+  Thank you for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please feel free to either reopen this issue or open a new one. We will be more than happy to look at it again! You can read more here: https://blog.phalcon.io/post/github-closing-old-issues
 # Comment to post when removing the stale label.
 # unmarkComment: >
 #   Your comment here.
 
 # Comment to post when closing a stale Issue or Pull Request.
 #closeComment: >
-#  Thank you for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please feel free to either reopen this issue or open a new one. We will be more than happy to look at it again! You can read more here: https://blog.phalconphp.com/post/github-closing-old-issues
+#  Thank you for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please feel free to either reopen this issue or open a new one. We will be more than happy to look at it again! You can read more here: https://blog.phalcon.io/post/github-closing-old-issues
 
 # Limit the number of actions per hour, from 1-30. Default is 30
 limitPerRun: 30

CODE_OF_CONDUCT.md

@@ -20,6 +20,6 @@ disagree.
 
 If ever conflict arises, please bring it to the attention of the maintainers 
 privately. You can always find us on our [Discord](https://phalcon.link/discord) 
-server or you can send us an email at team@phalconphp.com 
+server or you can send us an email at team@phalcon.io 
 
 The core team maintains the final decision on any conflict that may arise.

CONTRIBUTING.md

@@ -34,9 +34,9 @@ Please report bugs when you've exhausted all of the above options.
 ## Bug Report Checklist
 
 * Make sure you are using the latest released version of Phalcon before submitting a bug report. Bugs in versions older than the latest released one will not be addressed by the core team (so long as the version is not LTS).
-* If you have found a bug it is important to add relevant reproducibility information to your issue to allow us to reproduce the bug and fix it quicker. Add a script, small program or repository providing the necessary code to make everyone reproduce the issue reported easily. If a bug cannot be reproduced by the development it would be difficult provide corrections and solutions. [Submit Reproducible Test](https://docs.phalconphp.com/en/latest/reproducible-tests) for more information
+* If you have found a bug it is important to add relevant reproducibility information to your issue to allow us to reproduce the bug and fix it quicker. Add a script, small program or repository providing the necessary code to make everyone reproduce the issue reported easily. If a bug cannot be reproduced by the development it would be difficult provide corrections and solutions. [Submit Reproducible Test](https://docs.phalcon.io/en/latest/reproducible-tests) for more information
 * Be sure that information such as OS, Phalcon version and PHP version are part of the bug report
-* If you're submitting a [Segmentation Fault](https://en.wikipedia.org/wiki/Segmentation_fault) error, we would require a backtrace, please see [Generating a Backtrace](https://docs.phalconphp.com/en/latest/generating-backtrace)
+* If you're submitting a [Segmentation Fault](https://en.wikipedia.org/wiki/Segmentation_fault) error, we would require a backtrace, please see [Generating a Backtrace](https://docs.phalcon.io/en/latest/generating-backtrace)
 
 ## Pull Request Checklist
 
@@ -48,7 +48,7 @@ Please report bugs when you've exhausted all of the above options.
 
 ## Requesting Features
 
-If you have a change or new feature in mind, please fill a [NFR](https://docs.phalconphp.com/en/latest/new-feature-request) on the GitHub. Alternatively you may also request features via [the FeatHub page](https://feathub.com/phalcon/cphalcon).
+If you have a change or new feature in mind, please fill a [NFR](https://docs.phalcon.io/en/latest/new-feature-request) on the GitHub. Alternatively you may also request features via [the FeatHub page](https://feathub.com/phalcon/cphalcon).
 
 
 Thanks! <br />

appveyor.yml

@@ -1,6 +1,6 @@
 # This file is part of the Phalcon Framework.
 #
-# (c) Phalcon Team <team@phalconphp.com>
+# (c) Phalcon Team <team@phalcon.io>
 #
 # For the full copyright and license information, please view
 # the LICENSE.txt file that was distributed with this source code.

build/README.md

@@ -47,7 +47,7 @@ After running `gen-build.php` you are ready to build Phalcon extension.
 
 ## Building extension for Linux
 
-Please, refer to [Phalcon documentation](https://docs.phalconphp.com)
+Please, refer to [Phalcon documentation](https://phalcon.link/docs)
 
 
 ## Building extension for Windows

build/install

@@ -1,18 +1,11 @@
 #!/usr/bin/env bash
 #
-#  Phalcon Framework
+# This file is part of the Phalcon Framework.
 #
-#  Copyright (c) 2011-present Phalcon Team (https://phalconphp.com)
+# (c) Phalcon Team <team@phalcon.io>
 #
-#  This source file is subject to the New BSD License that is bundled
-#  with this package in the file LICENSE.txt.
-#
-#  If you did not receive a copy of the license and are unable to
-#  obtain it through the world-wide-web, please send an email
-#  to license@phalconphp.com so we can send you a copy immediately.
-#
-#  Authors: Andres Gutierrez <andres@phalconphp.com>
-#           Eduar Carvajal <eduar@phalconphp.com>
+# For the full copyright and license information, please view the LICENSE.txt
+# file that was distributed with this source code.
 #
 #  Available params:
 #  --arch
@@ -23,7 +16,7 @@
 #  ./install --phpize /usr/bin/phpize7.3 --php-config /usr/bin/php-config7.3 --arch 32bits
 
 # Check best compilation flags for GCC
-# By default we compile to be as compatible as possible with all processors. 
+# By default we compile to be as compatible as possible with all processors.
 # If you would like instruct the compiler to generate optimized machine code that matches the processor where it is currently running on you can set your own compile flags by exporting CFLAGS before the build.
 #
 # Example:
@@ -32,7 +25,7 @@
 # This will generate the best possible code for that chipset but will likely break the compiled object on older chipsets.
 
 export CC="gcc"
-if [ -z "$CFLAGS" ] 
+if [ -z "$CFLAGS" ]
 then
   export CFLAGS="-mtune=native -O2 -fomit-frame-pointer"
 fi