humhub · gevorgmansuryan · Sep 1, 2024 · Sep 2, 2024 · Sep 3, 2024 · Sep 4, 2024
diff --git a/docs/admin/installation.md b/docs/admin/installation.md
@@ -92,7 +92,7 @@ The following configuration settings can be made directly in HumHub via the brow
 
 HumHub sends emails to the users e.g. during the registration, password recovery, notifications or for daily summaries.
 
-A valid transport and a sender e-mail address must be provided for this purpose. This can be configured in the web interface under ``Administration -> Settings -> Advanced -> E-Mail`.
+A valid transport and a sender e-mail address must be provided for this purpose. This can be configured in the web interface under ``Administration > Settings > Advanced > E-Mail`.
 
 :::note
 You should use a `noreply` sender e-mail address sice reply by mail is currently not supported.
@@ -102,23 +102,6 @@ If you installed a local SMTP server e.g. [Postfix](server-setup.md#postfix), yo
 
 You can use external SMTP services like SendGrid, Postmark, Amazon SES, Mailgun or any other SMTP server with the ``SMTP`` as ``Mail Transport Type`` option. 
 
-### Time Zone
-
-By default HumHub uses the time zone of the web server. However, the time zone of the database server (MariaDB) is the relevant one. If these time zones differs or the server was moved to another location, you need to change this time zone.  
-
-You can switch the time zone at: ``Administration -> Settings -> General -> Server timezone``
-
-If you are not sure which time zone is configured on your Maria DB server, you can query the time zone with the following SQL statement.
-
-```sql
-mysql> SELECT @@global.time_zone, @@session.time_zone;
-``` 
-
-
-:::note
-Each registered user can also set its own primary time zone in the profile settings.
-:::
-
 ## Pretty URLs 
 
 By default, the HumHub URL includes a index.php file part and looks like https://example.com/index.php?r=dashboard%2Fdashboard. 
@@ -192,30 +175,20 @@ The [virtual server](server-setup.md#nginx) configuration for NGINX is already p
 
 ## Enable production mode
 
-By default HumHub is shipped in debug mode. This means that error messages are shown with maximum details directly to the users. In addition, the performance is reduced because no caching or compressed assets are used.
-
-To activate Production Mode, edit the index.php file  and comment out the following lines.
-To comment out lines, the line must begin with: //
+By default, HumHub is shipped in debug mode. After a successful installation, it automatically switches to production mode.
 
-Example (/var/www/humhub/index.php):
-
-```php
-// comment out the following two lines when deployed to production
-// defined('YII_DEBUG') or define('YII_DEBUG', true);
-// defined('YII_ENV') or define('YII_ENV', 'dev');
-``` 
+You can see the current mode at ``Administration > Information``.
 
-You can see the current mode at ``Administration -> Information``.
 
 ## Verify 
 
 - **Cronjobs**
 
-    You can find the last execution and number of open background jobs at: ``Administration -> Information -> Background jobs``
+    You can find the last execution and number of open background jobs at: ``Administration > Information > Background jobs``
 
 - **Error log**
 
-    Check the log for error messages and warnings. These can be viewed directly in Humhub under YXZ.  ``Administration -> Information -> Logging``
+    Check the log for error messages and warnings. These can be viewed directly in Humhub under YXZ.  ``Administration > Information > Logging``
 
 - **Protected folders**
 
@@ -229,7 +202,7 @@ You can see the current mode at ``Administration -> Information``.
 
 - **Production Mode**
 
-    Make sure that no warning about the ``Debug mode`` appears under ``Administration -> Information -> About HumHub``.
+    Make sure that no warning about the ``Debug mode`` appears under ``Administration > Information > About HumHub``.
 
  ## Staging/Test Environment
 

diff --git a/docs/admin/security.md b/docs/admin/security.md
@@ -8,21 +8,11 @@ This guide describes recommended configurations and practices in order to keep y
  Enable Production Mode
 --------------------------
 
-By default HumHub is operating in _DEBUG_ mode, which besides others uses a different error handling and non combined
-assets. Before opening your installation to the public you should enable the production mode first by commenting out the
-following lines of the `index.php` file within your HumHub root directory:
+1. By default, HumHub is shipped in debug mode. After a successful installation, it automatically switches to production mode.
+If you previously enabled ``DEBUG`` mode via the ``.env`` file, make sure that ``HUMHUB_DEBUG=0`` before opening your installation to the public.
+> If you do not have a ``.env`` file in the project root, you can skip this step.
 
-```php
-[...]
-// comment out the following two lines when deployed to production
-// defined('YII_DEBUG') or define('YII_DEBUG', true);
-// defined('YII_ENV') or define('YII_ENV', 'dev');
-[...]
-```
-
-> Note: In this example the lines are already commented out.
-
-You should also delete the `index-test.php` file in your HumHub root directory if existing.
+2. Delete the ``index-test.php`` file in your HumHub root directory if it exists.
 
 Protected Directories
 ---------------------
@@ -34,9 +24,9 @@ Limit User Access
 
 If you're running a private social network, make sure the user registration has been disabled or the approval system for new users has been enabled.
 
-- Disable user registration: `Administration -> Users -> Settings -> Anonymous users can register`
-- Enable user approvals: `Administration -> Users -> Settings -> Require group admin approval after registration`
-- Make sure guest access is disabled: `Administration -> Users -> Settings -> Allow limited access for non-authenticated users (guests)`
+- Disable user registration: `Administration > Users > Settings > Anonymous users can register`
+- Enable user approvals: `Administration > Users > Settings > Require group admin approval after registration`
+- Make sure guest access is disabled: `Administration > Users > Settings > Allow limited access for non-authenticated users (guests)`
 
 Password Strength Configuration
 -------------------------------
@@ -180,7 +170,7 @@ Please refer to the following links for more information about the CSP and the c
 
 `csp-report-only`:
 
-This section can be used to define a csp rule, which will only log violations to `Administration -> Information -> Logging`
+This section can be used to define a csp rule, which will only log violations to `Administration > Information > Logging`
 rather than blocking the resources on the client. This can be used to test csp rules on your installation.
 
 **CSP Reporting:**
@@ -207,7 +197,7 @@ properly with your security configuration, please contact the module owner or re
 
 This section assembles some guidelines and restrictions regarding custom CSP settings in HumHub.
 
-- The HumHub core currently requires `img-src data:` for page icon and image upload `Administration -> Settings -> Appearance`
+- The HumHub core currently requires `img-src data:` for page icon and image upload `Administration > Settings > Appearance`
 - When using the enterprise edition you should allow `https://www.humhub.org` for `frame-src`
 - When noticing any issues with external modules, please inform the module owner.
 - When developing custom modules, try to test against the strictest csp rules (see default acceptance test csp rules) and provide
@@ -220,6 +210,6 @@ As an admin you'll receive notifications about new HumHub releases. We strongly
 stable version if possible.
 Check the [update guide](updating.md) for more information about updating your HumHub installation.
 
-Furthermore, you should regularly check the `Administration -> Modules -> Available Updates` section for module updates. 
+Furthermore, you should regularly check the `Administration > Modules > Available Updates` section for module updates. 
 
 We take security very seriously, and we're continuously improving the security features of HumHub. 
diff --git a/docs/admin/troubleshooting.md b/docs/admin/troubleshooting.md
@@ -80,6 +80,15 @@ Support Community
 
 There is also an active support community at: http://community.humhub.com
 
+Debug Mode
+-----------------
+
+Enabling Debug Mode:
+1. Create a new file called ``.env`` in the project root.
+2. Copy the contents of ``.env.example`` into the newly created ``.env`` file.
+3. Ensure that the value of ``HUMHUB_DEBUG`` is set to ``1``.
+
+To see which mode HumHub is currently operating in, navigate to ``Administration > Information``. To access log entries, go to  ``Administration > Information > Logging``
 
 Github - Bugtracker
 -------------------

diff --git a/docs/develop/environment.md b/docs/develop/environment.md
@@ -51,9 +51,10 @@ Please refer to the [Installation Guide](../admin/installation.md) for further i
 
 ### Quick Notes
 
-- Make sure the `debug` mode is enabled (default), see [Enable Production Mode](../admin/security.md#enable-production-mode)
-- Disable caching under `Administration -> Settings -> Advanced -> Caching -> None`
-- Use file based mailing `Administration -> Settings -> Advanced -> E-Mail`
+- Copy the contents of ``.env.example`` into the newly created ``.env`` file.
+- Make sure the ``DEBUG`` mode is enabled (default), see [Enable Debug Mode](../admin/installation.md#enable-debug-mode)
+- Disable caching under ``Administration > Settings > Advanced > Caching > None``
+- Use file based mailing ``Administration > Settings > Advanced > E-Mail``
 
 ### Queue configuration
 
@@ -64,26 +65,28 @@ have to run `queue/run` command manually in order to execute queued tasks as not
 
 ### Module Loader Path
 
-The default path under which HumHub searches for installed modules is `@humhub/protected/modules`. Additional search paths
-can be configured within `@humhub/protected/config/common.php` as follows: 
+The default path where HumHub searches for installed modules is ``@humhub/protected/modules``. Additional search paths can be configured in the ``.env`` file as follows:
 
-```php
-// @humhub/protected/config/common.php
-return [
-    'params' => [
-        'moduleAutoloadPaths' => ['/some/folder/modules'],
-    ],
-]
+```env
+// @humhub/.env
+HUMHUB_CONFIG__PARAMS__MODULE_AUTOLOAD_PATHS=['/some/folder/modules', '/some/other-folder/modules']
 ```
 This separation should be done for custom modules which are not in [the marketplace](https://marketplace.humhub.com/)
 (e.g, `@app/custom-modules`) or for your development environment in order to define a central module directory
 for different test installations and prevent interference with marketplace modules.
 
 ### Yii Debug Module
 
-You may want to enable the [Yii Debug Module](http://www.yiiframework.com/doc-2.0/ext-debug-index.html) for detailed
-request and query debugging. Just add the following block to your local web configuration `protected/config/web.php`:
+You may want to enable the [Yii Debug Module](http://www.yiiframework.com/doc-2.0/ext-debug-index.html) for detailed request and query debugging. Just add the following block to your local web configuration::
+
+in `.env`
+```env
+// @humhub/.env
+HUMHUB_CONFIG__BOOSTRAP=['debug']
+HUMHUB_CONFIG__MODULES__DEBUG='{"class":"yii\\\debug\\\Module", "allowedIPs": ["127.0.0.1", "::1"]}'
+```
 
+or in `protected/config/web.php`
 ```php
 return [
     'bootstrap' => ['debug'],