Update documentation

Update README and CHANGELOG

CHANGELOG.md

@@ -5,7 +5,13 @@ All notable changes to the [Alteryx deploy](https://github.com/Akaizoku/alteryx-
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [1.1.2](https://github.com/Akaizoku/alteryx-deploy/releases/1.1.2) - Unreleased
+## [1.1.2](https://github.com/Akaizoku/alteryx-deploy/releases/1.1.2) - 2021-12-13
+
+UX improvements
+
+### Changed
+
+- Automatically update environment variables during restore (installation path, Gallery URL, etc.)
 
 ### Fixed
 
@@ -25,6 +31,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [1.1.0](https://github.com/Akaizoku/alteryx-deploy/releases/1.1.0) - 2021-11-21
 
+2021.4 hotfix
+
 ### Added
 
 - `Invoke-StartAlteryx` now checks for release version to ensure compatibility

README.md

@@ -301,11 +301,12 @@ Below are the steps to restore the Alteryx application database.
 2. Check backup path;
    - If backup file is an archive (.ZIP), extract files from archive.
    - If backup path is a directory, select most recent backup file (using [last write time](https://docs.microsoft.com/en-us/dotnet/api/system.io.filesysteminfo.lastwritetime)).
-3. Restore MongoDB database;
-4. Restore application configuration files;
+3. Restore application configuration files;
+4. Update configuration to match new environment;
 5. Restore controller token;
 6. Reset storage keys;
-7. Restart Alteryx Service (if it was running previously).
+7. Restore MongoDB database;
+8. Restart Alteryx Service (if it was running previously).
 
 ### Start