Skip to content
Snippets Groups Projects
Commit e8b4068d authored by Rajab Natshah's avatar Rajab Natshah
Browse files

Issue #2914093: Orderd the UPDATE.md file

parent 2e72848e
No related branches found
No related tags found
No related merge requests found
......@@ -80,9 +80,10 @@ while working on the project.
---
# Updating Varbase 8.4.08 to Varbase 8.4.09
## Updating files with Copy and Paste for Varbase 8.4.08 to Varbase 8.4.09
# Updating Varbase 8.4.09 to Varbase 8.4.10
## Updating files with Copy and Paste for Varbase 8.4.09 to Varbase 8.4.10
```
Given that we are at the drupal root folder for varbase
When we delete all drupal core folders and files
......@@ -101,7 +102,7 @@ Varbase Procedures to the varbase base code. not in any varbase-project or
files are the latest
When we delete the "vendor" folder
And we delete the "composer.lock" file
And we run the "composer require vardot/varbase:8.4.09" command
And we run the "composer require vardot/varbase:8.4.10" command
And wait for composer to finish work
Then we should not see any issues in the terminal
And we should see "Writing lock file" in the terminal
......@@ -110,14 +111,14 @@ Varbase Procedures to the varbase base code. not in any varbase-project or
Then we will be ready to update the active config and database.
```
## Updating the active config and database from Varbase 8.4.08 to Varbase 8.4.09
## Updating the active config and database from Varbase 8.4.09 to Varbase 8.4.10
```
Given that we are in the docroot of the current Varbase project
And all files are updated using (copy and past) or (composer require/update
When we run drush "updb" or go to "/update.php"
Then we should see the steps of updates.
When we run drush "updb" or go to "/update.php" again
Then we will have the site update with the new Varbase 8.4.09 version
Then we will have the site update with the new Varbase 8.4.10 version
When we go to "/admin/config/development/features"
Then we should see "Changed"
When we follow with each feature to import new changes.
......@@ -125,10 +126,9 @@ Varbase Procedures to the varbase base code. not in any varbase-project or
```
# Updating Varbase 8.4.08 to Varbase 8.4.09
# Updating Varbase 8.4.09 to Varbase 8.4.10
## Updating files with Copy and Paste for Varbase 8.4.09 to Varbase 8.4.10
## Updating files with Copy and Paste for Varbase 8.4.08 to Varbase 8.4.09
```
Given that we are at the drupal root folder for varbase
When we delete all drupal core folders and files
......@@ -147,7 +147,7 @@ Varbase Procedures to the varbase base code. not in any varbase-project or
files are the latest
When we delete the "vendor" folder
And we delete the "composer.lock" file
And we run the "composer require vardot/varbase:8.4.10" command
And we run the "composer require vardot/varbase:8.4.09" command
And wait for composer to finish work
Then we should not see any issues in the terminal
And we should see "Writing lock file" in the terminal
......@@ -156,14 +156,14 @@ Varbase Procedures to the varbase base code. not in any varbase-project or
Then we will be ready to update the active config and database.
```
## Updating the active config and database from Varbase 8.4.09 to Varbase 8.4.10
## Updating the active config and database from Varbase 8.4.08 to Varbase 8.4.09
```
Given that we are in the docroot of the current Varbase project
And all files are updated using (copy and past) or (composer require/update
When we run drush "updb" or go to "/update.php"
Then we should see the steps of updates.
When we run drush "updb" or go to "/update.php" again
Then we will have the site update with the new Varbase 8.4.10 version
Then we will have the site update with the new Varbase 8.4.09 version
When we go to "/admin/config/development/features"
Then we should see "Changed"
When we follow with each feature to import new changes.
......@@ -173,6 +173,8 @@ Varbase Procedures to the varbase base code. not in any varbase-project or
# Updating Varbase 8.4.07 to Varbase 8.4.08
## Updating files with Copy and Paste for Varbase 8.4.07 to Varbase 8.4.08
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment