Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
N
noblogs-wp
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
39
Issues
39
List
Boards
Labels
Service Desk
Milestones
Merge Requests
1
Merge Requests
1
Operations
Operations
Incidents
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
ai
noblogs-wp
Commits
97524229
Commit
97524229
authored
Dec 19, 2014
by
ale
Committed by
agata
Oct 17, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add some upgrade instructions
parent
8f6d30bc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
43 additions
and
0 deletions
+43
-0
README.md
README.md
+43
-0
No files found.
README.md
View file @
97524229
...
...
@@ -244,6 +244,49 @@ cluster if you add or remove one backend, moving databases and blogs
around.
Upgrades
--------
The upgrade procedure involves upgrading the source repository on all
your servers, and running database upgrades for each blog. In order to
upgrade your installation, you will need the
`noblogs`
tool from the
`noblogs-cli`
repository.
### Upgrading the source code
We rebase our patch set on top of the Wordpress upstream on every
release, creating a new versioned branch of our repository. So the
first step is to figure out the most recent version is (our versioning
does not necessarily follow the Wordpress versioning scheme): you can
check the available branches in the git web interface for this
repository. At the time of this writing, the current version is
`noblogs-2.1.10`
, which we will use in the example below.
The following commands should upgrade your installation in place:
$ git remote update
$ git fetch noblogs-2.1.10
### Running database upgrades
The Network Upgrade option from the Wordpress admin panel does not
really work reliably, especially on large installations (due to request
timeouts and memory issues), so it is advised to use the
`noblogs`
command-line tool to perform post-upgrade maintenance tasks.
Assuming you have installed
`noblogs-cli`
in
`/opt/noblogs`
, the
following commands will upgrade the database schema for all blogs:
$ /opt/noblogs/bin/on-all-blogs upgrade
Note that this requires passwordless SSH access to the backend
servers. Otherwise you can always run
$ /opt/noblogs/bin/on-local-blogs upgrade
manually on each backend.
Contributing to the project
---------------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment