update installation docs

Author: totoprayogo1916

user_guide_src/source/installation/index.rst

@@ -26,7 +26,7 @@ However you choose to install and run CodeIgniter4, the
 `user guide <https://codeigniter4.github.io/userguide/>`_ is accessible online.
 
 .. note:: Before using CodeIgniter 4, make sure that your server meets the
-          :doc:`requirements </intro/requirements>`, in particular the PHP
-          version and the PHP extensions that are needed.
-          You may find that you have to uncomment the ``php.ini`` "extension"
-          lines to enable "curl" and "intl", for instance.
+    :doc:`requirements </intro/requirements>`, in particular the PHP
+    version and the PHP extensions that are needed.
+    You may find that you have to uncomment the ``php.ini`` "extension"
+    lines to enable "curl" and "intl", for instance.

user_guide_src/source/installation/installing_composer.rst

@@ -1,5 +1,5 @@
 Composer Installation
-###############################################################################
+#####################
 
 .. contents::
     :local:
@@ -18,7 +18,7 @@ webapp,
    when you clone the repository to a new system.
 
 App Starter
-============================================================
+===========
 
 The `CodeIgniter 4 app starter <https://github.com/codeigniter4/appstarter>`_
 repository holds a skeleton application, with a composer dependency on
@@ -28,7 +28,7 @@ This installation technique would suit a developer who wishes to start
 a new CodeIgniter4 based project.
 
 Installation & Set Up
--------------------------------------------------------
+---------------------
 
 In the folder above your project root::
 
@@ -51,7 +51,7 @@ A sample such installation command, using the default project-root "appstarter":
 After installation you should follow the steps in the "Upgrading" section.
 
 Upgrading
--------------------------------------------------------
+---------
 
 Whenever there is a new release, then from the command line in your project root::
 
@@ -71,17 +71,17 @@ would be appropriate to do so here too, i.e., ``composer update --no-dev``.
 Read the upgrade instructions, and check designated  ``app/Config`` folders for affected changes.
 
 Pros
--------------------------------------------------------
+----
 
 Simple installation; easy to update
 
 Cons
--------------------------------------------------------
+----
 
 You still need to check for ``app/Config`` changes after updating
 
 Structure
--------------------------------------------------------
+---------
 
 Folders in your project after set up:
 
@@ -90,7 +90,7 @@ Folders in your project after set up:
 - vendor/codeigniter4/framework/app & public (compare with yours after updating when using ``--prefer-source``)
 
 Latest Dev
--------------------------------------------------------
+----------
 
 The App Starter repo comes with a ``builds`` scripts to switch Composer sources between the
 current stable release and the latest development branch of the framework. Use this script
@@ -114,7 +114,7 @@ After using the ``builds`` command be sure to run ``composer update`` to sync yo
 folder with the latest target build.
 
 Adding CodeIgniter4 to an Existing Project
-============================================================
+==========================================
 
 The same `CodeIgniter 4 framework <https://github.com/codeigniter4/framework>`_
 repository described in "Manual Installation" can also be added to an
@@ -131,7 +131,7 @@ As with the earlier two composer install methods, you can omit installing
 phpunit and its dependencies by adding the ``--no-dev`` argument to the ``composer require`` command.
 
 Set Up
--------------------------------------------------------
+------
 
 Copy the ``app``, ``public``, and ``writable`` folders from ``vendor/codeigniter4/framework``
 to your project root
@@ -143,7 +143,7 @@ You will have to adjust the system path to refer to the vendor one, e.g., ``ROOT
 - the ``$systemDirectory`` variable in ``app/Config/Paths.php``
 
 Upgrading
--------------------------------------------------------
+---------
 
 Whenever there is a new release, then from the command line in your project root::
 
@@ -153,17 +153,17 @@ Read the upgrade instructions, and check designated
 ``app/Config`` folders for affected changes.
 
 Pros
--------------------------------------------------------
+----
 
 Relatively simple installation; easy to update
 
 Cons
--------------------------------------------------------
+----
 
 You still need to check for ``app/Config`` changes after updating
 
 Structure
--------------------------------------------------------
+---------
 
 Folders in your project after set up:
 
@@ -172,7 +172,7 @@ Folders in your project after set up:
 
 
 Translations Installation
-============================================================
+=========================
 
 If you want to take advantage of the system message translations,
 they can be added to your project in a similar fashion.

user_guide_src/source/installation/installing_manual.rst

@@ -1,5 +1,5 @@
 Manual Installation
-###############################################################################
+###################
 
 The `CodeIgniter 4 framework <https://github.com/codeigniter4/framework>`_
 repository holds the released versions of the framework.
@@ -13,18 +13,18 @@ folder!
    for `CodeIgniter 3 <https://codeigniter.com/user_guide/installation/index.html>`_.
 
 Installation
-============================================================
+============
 
 Download the `latest version <https://github.com/CodeIgniter4/framework/releases/latest>`_,
 and extract it to become your project root.
 
 Setting Up
--------------------------------------------------------
+----------
 
 None
 
 Upgrading
--------------------------------------------------------
+---------
 
 Download a new copy of the framework, and then follow the upgrade
 instructions in the release notice or changelog to merge that with your project.
@@ -33,24 +33,24 @@ Typically, you replace the ``system`` folder, and check designated
 ``app/Config`` folders for affected changes.
 
 Pros
--------------------------------------------------------
+----
 
 Download and run
 
 Cons
--------------------------------------------------------
+----
 
 You are responsible for merge conflicts when updating
 
 Structure
--------------------------------------------------------
+---------
 
 Folders in your project after set up:
 app, public, system, writable
 
 
 Translations Installation
-============================================================
+=========================
 
 If you want to take advantage of the system message translations,
 they can be added to your project in a similar fashion.

user_guide_src/source/installation/running.rst

@@ -1,5 +1,5 @@
 Running Your App
-###############################################################################
+################
 
 .. contents::
     :local:
@@ -13,7 +13,7 @@ If you’re new to CodeIgniter, please read the :doc:`Getting Started </intro/in
 section of the User Guide to begin learning how to build dynamic PHP applications. Enjoy!
 
 Initial Configuration & Set Up
-=================================================
+==============================
 
 #. Open the **app/Config/App.php** file with a text editor and
    set your base URL. If you need more flexibility, the baseURL may
@@ -37,7 +37,7 @@ to "development".
     web server.
 
 Local Development Server
-=================================================
+========================
 
 CodeIgniter 4 comes with a local development server, leveraging PHP's built-in web server
 with CodeIgniter routing. You can use the ``serve`` script to launch it,
@@ -71,7 +71,7 @@ The local development server can be customized with three command line options:
     php spark serve --php /usr/bin/php7.6.5.4
 
 Hosting with Apache
-=================================================
+===================
 
 A CodeIgniter4 webapp is normally hosted on a web server.
 Apache’s ``httpd`` is the "standard" platform, and assumed in much of our documentation.
@@ -80,7 +80,7 @@ Apache is bundled with many platforms, but can also be downloaded in a bundle
 with a database engine and PHP from `Bitnami <https://bitnami.com/stacks/infrastructure>`_.
 
 .htaccess
--------------------------------------------------------
+---------
 
 The “mod_rewrite” module enables URLs without “index.php” in them, and is assumed
 in our user guide.
@@ -100,7 +100,7 @@ in the "AllowOverride" setting::
     </Directory>
 
 Virtual Hosting
--------------------------------------------------------
+---------------
 
 We recommend using “virtual hosting” to run your apps.
 You can set up different aliases for each of the apps you work on,
@@ -130,14 +130,14 @@ If your project folder is not a subfolder of the Apache document root, then your
 <VirtualHost> element may need a nested <Directory> element to grant the web server access to the files.
 
 Testing
--------------------------------------------------------
+-------
 
 With the above configuration, your webapp would be accessed with the URL ``http://myproject.local`` in your browser.
 
 Apache needs to be restarted whenever you change its configuration.
 
 Hosting with Nginx
-=================================================
+==================
 Nginx is the second most widely used HTTP server for web hosting.
 Here you can find an example configuration using PHP 7.3 FPM (unix sockets) under Ubuntu Server.
 
@@ -176,7 +176,7 @@ This configuration enables URLs without “index.php” in them and using CodeIg
     }
 
 Hosting with Vagrant
-=================================================
+====================
 
 Virtualization is an effective way to test your webapp in the environment you
 plan to deploy on, even if you develop on a different one.
@@ -187,7 +187,7 @@ The codebase comes with a ``VagrantFile.dist``, that can be copied to ``VagrantF
 and tailored for your system, for instance enabling access to specific database or caching engines.
 
 Setting Up
--------------------------------------------------------
+----------
 
 It assumes that you have installed `VirtualBox <https://www.virtualbox.org/wiki/Downloads>`_ and
 `Vagrant <https://www.vagrantup.com/downloads.html>`_
@@ -199,7 +199,7 @@ The Vagrant configuration file assumes you have set up a `ubuntu/bionic64 Vagran
     vagrant box add ubuntu/bionic64
 
 Testing
--------------------------------------------------------
+-------
 
 Once set up, you can then launch your webapp inside a VM, with the command::
 
@@ -210,7 +210,7 @@ report for your build at ``http://localhost:8081`` and the user guide for
 it at ``http://localhost:8082``.
 
 Bootstrapping the App
-=================================================
+=====================
 
 In some scenarios you will want to load the framework without actually running the whole
 application. This is particularly useful for unit testing your project, but may also be

user_guide_src/source/installation/troubleshooting.rst

@@ -5,7 +5,7 @@ Troubleshooting
 Here are some common installation problems, and suggested workarounds.
 
 How do I know if my install is working?
-------------------------------------------------------------------------
+---------------------------------------
 
 From the command line, at your project root::
 
@@ -55,7 +55,7 @@ CodeIgniter equivalent, ``php spark serve`` from your project root.
 .. |CodeIgniter4 Welcome| image:: ../images/welcome.png
 
 What's with an unhelpful "Whoops!" page?
-------------------------------------------------------
+----------------------------------------
 
 You find that your app is displaying a page with "Whoops!" and
 then the text line "We seem to have hit a snag. Please try again later...".
@@ -70,7 +70,7 @@ You can see the error in the debug toolbar display by setting your environment t
 Don't forget to reset the environment to "production" once you fix the problem!
 
 CodeIgniter Error Logs
--------------------------------------------------------
+----------------------
 
 CodeIgniter logs error messages, according to the settings in `app/Config/Logger.php`.
 

user_guide_src/source/installation/upgrade_412.rst

@@ -1,6 +1,6 @@
-######################################
+#############################
 Upgrading from 4.1.1 to 4.1.2
-######################################
+#############################
 
 **BaseConnection::query() return values**
 
@@ -9,7 +9,7 @@ even if the query failed. This method will now return ``false`` for failed queri
 Exception if ``DBDebug==true``) and will return booleans for write-type queries. Review any use
 of ``query()`` method and be assess whether the value might be boolean instead of Result object.
 For a better idea of what queries are write-type queries, check ``BaseConnection::isWriteType()``
-and any DBMS-specific override ``isWriteType()`` in the relevant Connection class. 
+and any DBMS-specific override ``isWriteType()`` in the relevant Connection class.
 
 **ConnectionInterface::isWriteType() declaration added**
 
@@ -26,24 +26,24 @@ classes have been deprecated and their methods moved to ``DatabaseTestTrait`` an
 ``FeatureTestTrait`` respectively. Update your test cases to extend the main test case
 and use any traits you need. For example::
 
-	use CodeIgniter\Test\DatabaseTestCase;
+    use CodeIgniter\Test\DatabaseTestCase;
 
-	class MyDatabaseTest extends DatabaseTestCase
-	{
-		public function testBadRow()
-		{
+    class MyDatabaseTest extends DatabaseTestCase
+    {
+        public function testBadRow()
+        {
 
 ... becomes::
 
-	use CodeIgniter\Test\CIUnitTestCase;
-	use CodeIgniter\Test\DatabaseTestTrait;
+    use CodeIgniter\Test\CIUnitTestCase;
+    use CodeIgniter\Test\DatabaseTestTrait;
 
-	class MyDatabaseTest extends CIUnitTestCase
-	{
-		use DatabaseTestTrait;
+    class MyDatabaseTest extends CIUnitTestCase
+    {
+        use DatabaseTestTrait;
 
-		public function testBadRow()
-		{
+        public function testBadRow()
+        {
 
 Finally, ``ControllerTester`` has been superseded by ``ControllerTestTrait`` to standardize
 approach and take advantage of the updated response testing (below).
@@ -55,5 +55,6 @@ The tools for testing responses have been consolidated and improved. A new
 set of methods and properties expected from both those classes. In most cases these changes
 will be "behind the scenes" by ``ControllerTestTrait`` and ``FeatureTestCase``, but two
 changes to be aware of:
+
 * ``TestResponse``'s ``$request`` and ``$response`` properties are protected and should only be access through their getter methods, ``request()`` and ``response()``
 * ``TestResponse`` does not have ``getBody()`` and ``setBody()`` methods, but rather uses the Response methods directly, e.g.: ``$body = $result->response()->getBody();``