* Added possiblity to connect to redis via a unix socket
* Improved redis via socket config usage and added config option to blueprints
* Updated Changelog
* Improved redis via socket by adding a default value and a placeholder in the blueprint
* GPM: SSL verify peer and method (auto|fopen|curl) are now settings
* Added Admin blueprints settings
* Fixed default verify_peer value
* Fixed lang references for verify_peer
* Minor fixes for improper comments default values
* initial push of DirectInstall command
* Refactored to support direct-install
* added info about dependencies, and continue question
* Cleanup per @w00fz comments
* put Grav destination check back.
By setting `custom_base_url` in system.yaml, we can have Grav in a subfolder but run it in the domain root.
## Scenario 1
Grav is installed in `http://localhost:8080/grav-develop` but you want it to respond on `http://localhost:8080`
In system.yaml, set
```
custom_base_url: 'http://localhost:8080'
```
and set the session path to the new Grav site path,
```
session:
path: /
```
And in the domain root, set the redirect, e.g. with .htaccess:
```
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/grav-develop/
RewriteRule ^(.*)$ /grav-develop/$1
```
where `grav-develop` is the subfolder where Grav is.
## Scenario 2
Grav is installed in `http://localhost:8080/grav-develop` but you want it to respond on `http://localhost:8080/xxxxx`
In system.yaml, set
```
custom_base_url: 'http://localhost:8080/xxxxx'
```
and set the session path to the new Grav site path,
```
session:
path: /xxxxx
```
And in the new root folder, /xxxxx, set the redirect, e.g. with .htaccess:
```
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/grav-develop/
RewriteRule ^(.*)$ /grav-develop/$1
```
where `grav-develop` is the sister subfolder where Grav is.
`tmp` is a new folder that serves as container for temporary files. It is very similar to `cache` but its content is meant to be more persistent than cache. Temporary files are meant to survive cache clearance, developers should be responsible of ensuring temporary files are properly removed when needed.
Accessible via stream `tmp://`.
Can be cleared with `bin/grav clear --tmp-only` as well as `--all`.
