From Fedora Project Wiki
(Created page with "{{admon/warning | THIS PAGE IS NOT READY | Don't follow these instructions for anything yet. This page is still under construction and needs to be fact checked for accuracy.}}...")
 
Line 17: Line 17:
</pre>
</pre>


Repeat the `curl` command for each plugin that requires an update.
Repeat the <code>curl</code> command for each plugin that requires an update.


== Updating WordPress ==
== Updating WordPress ==


(TBD, basically you can do this at the CLI as well but you also have to restart the gears.)
(TBD, basically you can do this at the CLI as well but you also have to restart the gears.)

Revision as of 13:41, 31 July 2015

Warning.png
THIS PAGE IS NOT READY
Don't follow these instructions for anything yet. This page is still under construction and needs to be fact checked for accuracy.
Note.png
For administrators only
If you're not a Magazine administrator, the procedures described here probably won't work for you. Please don't mess around with the Magazine unless you're reasonably sure you know what you're doing. Remember that the Magazine serves many thousands of people every day!

Logging in

ssh ...

Updating plugins

Plugins must be updated through a remote SSH session at the command line. However, the procedure is much the same as with any other self-hosted WordPress instance. The folder location is based on the fact that the Magazine runs on OpenShift.

ssh ...
cd ...
curl -s -o - http://<link to new plugin .tar.gz> | tar xz

Repeat the curl command for each plugin that requires an update.

Updating WordPress

(TBD, basically you can do this at the CLI as well but you also have to restart the gears.)