Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
varbase
Manage
Activity
Members
Labels
Plan
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
project
varbase
Commits
e8b4068d
Commit
e8b4068d
authored
7 years ago
by
Rajab Natshah
Browse files
Options
Downloads
Patches
Plain Diff
Issue
#2914093
: Orderd the UPDATE.md file
parent
2e72848e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
UPDATE.md
+13
-11
13 additions, 11 deletions
UPDATE.md
with
13 additions
and
11 deletions
UPDATE.md
+
13
−
11
View file @
e8b4068d
...
...
@@ -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.0
9
" command
And we run the "composer require vardot/varbase:8.4.
1
0" 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.0
8
to Varbase 8.4.0
9
## Updating the active config and database from Varbase 8.4.0
9
to Varbase 8.4.
1
0
```
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.0
9
version
Then we will have the site update with the new Varbase 8.4.
1
0 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.
1
0" command
And we run the "composer require vardot/varbase:8.4.0
9
" 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.0
9
to Varbase 8.4.
1
0
## Updating the active config and database from Varbase 8.4.0
8
to Varbase 8.4.0
9
```
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.
1
0 version
Then we will have the site update with the new Varbase 8.4.0
9
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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment