Small improvements for the installation process (#199)

* ext-intl as required in composer, more details to explain the installation process

* Typo fixed

* Using better utf8 mysql support

composer.json

@@ -31,6 +31,7 @@
         "ext-session": "*",
         "ext-spl": "*",
         "ext-simplexml": "*",
+        "ext-intl": "*",
         "symfony/polyfill-php73":  "^1.9",
         "ezsystems/ezpublish-legacy-installer": "*",
         "zetacomponents/archive": "~1.5",

doc/INSTALL.md

@@ -4,13 +4,20 @@ Lovestack installation instructions
 With composer
 --
 
-* Install composer (https://getcomposer.org/)
-* Clone this repository `git clone https://github.com/mugoweb/ezpublish-legacy.git`
-* Optional: Edit the file `composer.json` and adjust it to your needs. For example add eZ Publish extensions into the 'required' section. 
-* Execute 'composer install' - it will install all required dependencies
-* Use [this vhost configuration file](/doc/apache2/legacy.conf) as an example to configure Apache
-* Use a web browser to access the Lovestack application
-* Follow the instructions of the web installation wizard
+1) Install composer (https://getcomposer.org/)
+1) Clone this repository `git clone https://github.com/mugoweb/ezpublish-legacy.git`
+1) Optional: Edit the file `composer.json` and adjust it to your needs. For example add eZ Publish extensions into the 'required' section. 
+1) Execute 'composer install' - it will install all required dependencies
+1) Use [this vhost configuration file](/doc/apache2/legacy.conf) as an example to configure Apache
+1) Create a database - following example is for mysql
+   ```
+   CREATE DATABASE ezpublish charset utf8mb4;
+   CREATE USER 'ezpublish'@'localhost' IDENTIFIED BY 'secretPassword';
+   GRANT ALL PRIVILEGES ON * . * TO 'ezpublish'@'localhost';
+   FLUSH PRIVILEGES;
+   ```
+1) Use a web browser to access the Lovestack application
+1) Follow the instructions of the web installation wizard
 
 Moving the code base to a different repository
 --
@@ -19,4 +26,4 @@ Most likely you want to push the code base to a new code repository. You can do
 * clone the new repository on top of the existing code base
 * commit and push all files into the new repository
 
-It's a good idea to _Store the commit hash in eZ Publish_. See [update/README.md](/update/README.md)
+It's a good idea to _Store the commit hash in eZ Publish_. See [update/README.md](/update/README.md#store-the-commit-hash-in-ez-publish)

update/README.md

@@ -87,8 +87,8 @@ running. You get the commit hash with the command `git rev-parse HEAD`.
 That hash string needs to be added to `lib/version.php`.
 
 ```
-cd /tmp/ezpublish-legacy
-sed -i "/const GIT_COMMIT_HASH = '.*';/c\    const GIT_COMMIT_HASH = '$(git rev-parse HEAD)';" /var/www/ezp/lib/version.php
+cd /var/www/ezp
+sed -i "/const GIT_COMMIT_HASH = '.*';/c\    const GIT_COMMIT_HASH = '$(git rev-parse HEAD)';" lib/version.php
 ```
 
 Notes about zeta components