* Fixes to allow not just ‘default/file’ cache in CLI
* vendor updates
* Better solution
* Added cli_compatibility to system blueprint
* Fall back to ‘file’ if cli_compatibility and (auto or volatile)
* Auto-adjust images orientation using EXIF data
* Fix composer.json
* Drop Excerpts edit
* Restore automatic orientation fix
* Revert "Restore automatic orientation fix"
This reverts commit 4b8af1fe72.
* Add auto orientation capability to images. Defaults to false to avoid forcing cache on every image
* Changelog
* 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
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.
When stored in the user config, configuration for collections might
still reference old shipped releases. We move to jquery-2.x.min.js for
all future 2.x releases, and we'll have a jquery-3.x.min.js when it's
shipped.
