summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Lange <code@nerdmind.de>2017-10-23 02:12:23 +0200
committerThomas Lange <code@nerdmind.de>2017-10-23 02:12:23 +0200
commit8167064c143237bb0f7d387c78b64b91b2d67f32 (patch)
treea964bf1c4e556b9311827b2cebc736ddba8ca942
parent86fcdd73201ae93ed362f587b6fdea1ec8d64ad5 (diff)
downloadwiki-8167064c143237bb0f7d387c78b64b91b2d67f32.tar.gz
wiki-8167064c143237bb0f7d387c78b64b91b2d67f32.tar.xz
wiki-8167064c143237bb0f7d387c78b64b91b2d67f32.zip
Spelling mistakes fixed and hyperlinks to the current supported MySQL version updated.
-rw-r--r--Configuration.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/Configuration.md b/Configuration.md
index 5be1bb9..b50cbf6 100644
--- a/Configuration.md
+++ b/Configuration.md
@@ -6,7 +6,7 @@ This is the core language which will be used. A corresponding language file **mu
* `CORE.LANGUAGE`: [string: `'en'`]
## ETag configuration
-If this parameter is set to `TRUE`, the system will generate an `ETag` header which includes a hash of the configuration and the timestamps of the last published items and sends them to the client. The client will cache this header and sends them with each further request in the request header to the application. If the hash which the appplication now again creates is not the same as the one from the request header (which means that no new items was published), the application exit and returns the `304 Not Modified` response header.
+If this parameter is set to `TRUE`, the system will generate an `ETag` response header which includes a hash of the timestamps from the last created / edited items and sends him to the client. The client will cache this header and sends him with each further request in the request header back to the application. If the hash, which the appplication now creates again, is not the same as the one from the request header (which means that no new items have been published and no existing item have been edited), the application exit and returns the `304 Not Modified` response header to reduce server load and traffic.
* `CORE.SEND_304`: [boolean: `TRUE`|`FALSE`]
@@ -20,7 +20,7 @@ Meta informations about your custom blog installation. Note that `BLOGMETA.LANG`
* `BLOGMETA.LANG`: [string: `'en'`]
## Database
-Database and hostname with login credentials to authenticate to the MySQL server.
+Database and hostname with login credentials to authenticate to the MariaDB or MySQL server.
* `DATABASE.HOSTNAME`: [string: `'localhost'`]
* `DATABASE.BASENAME`: [string: `'niceblog'`]
@@ -28,7 +28,7 @@ Database and hostname with login credentials to authenticate to the MySQL server
* `DATABASE.PASSWORD`: [string: `'#passwd#'`]
## Backend
-Settings for administration area. A corresponding language file **must exists** within the template directory of the template defined by `ADMIN.TEMPLATE`!
+Settings for the administration area. A corresponding language file **must exists** within the template directory of the template defined by `ADMIN.TEMPLATE`!
* `ADMIN.TEMPLATE`: [string: `'admin'`]
* `ADMIN.LANGUAGE`: [string: `'en'`]
@@ -40,7 +40,7 @@ Template directory and language (from `template/{template_name}/lang/`) to use.
* `TEMPLATE.LANG`: [string: `'en'`]
## Paths
-Protocol, hostname and base directory for your installation.
+Protocol, hostname and base directory of your installation.
* `PATHINFO.PROT`: [string: `'https'`]
* `PATHINFO.HOST`: [string: `'example.org'`]
@@ -88,16 +88,16 @@ Number of characters from the items content to display within the `<meta>` descr
* `USER.DESCRIPTION_SIZE`: [integer: `200`]
## Item overview sorting
-The `ORDER BY` clause for item sorting on item overview sites. You can use each column from the database table to sort and you also can combine multiple columns together. See the [MySQL documentation for `ORDER BY`](https://dev.mysql.com/doc/refman/5.5/en/sorting-rows.html) for more information.
+The `ORDER BY` clause for item sorting on item overview sites. You can use each column from the database table to sort and you also can combine multiple columns together. See the [MySQL documentation for `ORDER BY`](https://dev.mysql.com/doc/refman/5.6/en/sorting-rows.html) for more information.
* `PAGE.LIST_SORT`: [string: `'time_insert DESC'`]
* `POST.LIST_SORT`: [string: `'time_insert DESC'`]
* `USER.LIST_SORT`: [string: `'time_insert DESC'`]
## Feed sorting
-The `ORDER BY` clause for item sorting within the RSS feed. You can use each column from the database table to sort and you also can combine multiple columns together. See the [MySQL documentation for `ORDER BY`](https://dev.mysql.com/doc/refman/5.5/en/sorting-rows.html) for more information.
+The `ORDER BY` clause for item sorting within the RSS feed. You can use each column from the database table to sort and you also can combine multiple columns together. See the [MySQL documentation for `ORDER BY`](https://dev.mysql.com/doc/refman/5.6/en/sorting-rows.html) for more information.
-**Note:** It depends on the RSS reader how the content is sorted. The settings here are only for the sorting of the content in the XML source code, but it is nevertheless a good idea to sort them as they should appear in the RSS reader.
+**Note:** It depends on the RSS reader how the content is sorted. The settings here are only for the sorting of the content in the raw XML source code, but it is nevertheless a good idea to sort them as they shall appear in the RSS reader.
* `PAGE.FEED_SORT`: [string: `'time_insert DESC'`]
* `POST.FEED_SORT`: [string: `'time_insert DESC'`]