welcome: please sign in

The following 302 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
able   access   accessing   according   account   Account   add   adding   admin   administrators   allow   also   and   anyone   anyuser   anywhere   api   article   as   at   be   but   by   can   Category   check   client   co   code   codex   com   command   complete   config   configure   Configure   configured   content   Contents   cookie   Coop   copy   core   create   Create   Createa   created   creates   Creating   current   daemon   Database   database   Databases   dbtool   define   delete   detailed   development   different   direct   directly   directories   directory   do   documentation   Dom   Domtool   done   downloading   drop   early   editing   enable   Enabling   entry   everything   Examples   except   execute   executing   features   file   Files   files   filesystem   first   folder   folders   Follow   following   Foot   for   force   free   from   fs   fsr   Get   good   grant   guide   handles   hardening   harder   has   have   Hcoop   here   home   host   how   htaccess   html   http   https   if   If   in   In   incompatible   inherit   initial   install   installation   installations   installing   Installing   instructions   is   it   It   jetpack   Jetpack   just   Just   keep   key   later   latest   limits   line   listing   lives   ll   local   location   makes   making   management   manager   Manager   Manual   many   may   me   Member   mkdir   mode   moment   most   My   mysql   name   naturally   Navigate   need   net   new   no   none   not   Note   now   Now   Of   of   on   one   open   Open   openafs   org   organized   our   ourselves   over   owner   page   parent   part   password   performed   permissions   php   phrase   Plugin   plugin   pointless   popular   practice   Press   prevents   privileges   probably   process   provide   public   put   rather   reading   result   rlk   root   Run   sa   salt   salts   same   save   second   secret   server   set   setacl   setting   setup   several   shell   should   since   site   So   so   software   some   source   Source   stable   Stable   store   Subversion   support   svn   system   Table   tags   tests   than   that   The   the   then   This   this   through   Tips   To   to   Tool   track   Tracking   Transferring   true   trunk   unique   up   Updating   upload   uploads   use   user   Using   using   version   Versions   via   visit   Visit   want   way   we   weblog   well   where   which   widely   will   with   Without   without   Word   Wordpress   wordpress   work   working   would   wp   write   You   you   your  

Clear message
Edit

MemberManual / WebApplications / WordPress

Wordpress is a free and open source content management system that is widely popular. This page will provide you with detailed instructions on how to install Wordpress using DomTool and AFS permissions.

This will guide you through downloading the latest stable version via Subversion, hardening permissions in the filesystem, and making a Domtool entry for the site.

1. Get the Source

If you have the OpenAFS client configured, you can set up Wordpress on your local system for the most part. The setup can (naturally) be performed on our shell server as well.

fsr setacl . system:anyuser none
fsr sa . $USER.daemon rlk

The first command makes it so that no one that you do not allow (except administrators) may access your Wordpress directory. The second command limits the privileges that the server software have over the directory to just reading, listing files, and executing code.

svn co https://core.svn.wordpress.org/tags/$VERSION .

mkdir wp-content/uploads
fs sa wp-content/uploads $USER.daemon write

2. Configure Wordpress

# in wp-config.php
define('DB_NAME', '$USER_$DB');
define('DB_USER', '$USER');
define('DB_PASSWORD', 'XXXXX your mysql password XXXXX');
define('DB_HOST', 'mysql');

# visit https://api.wordpress.org/secret-key/1.1/salt/ to generate cookie salts, and copy/paste result over:
define('AUTH_KEY',         'put your unique phrase here');
define('SECURE_AUTH_KEY',  'put your unique phrase here');
define('LOGGED_IN_KEY',    'put your unique phrase here');
define('NONCE_KEY',        'put your unique phrase here');
define('AUTH_SALT',        'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT',   'put your unique phrase here');
define('NONCE_SALT',       'put your unique phrase here');

You should now have a working weblog.

3. Enabling the Plugin Manager

To use the plugin manager you have to allow your daemon user to write to the wp-content directory in your installation.

fsr sa wp-content/ $USER.daemon write

The way Wordpress tests if it can directly write files is incompatible with openafs1, so you'll need to force it to directly write the file system by adding a line to your wp-config.php:

define('FS_METHOD', 'direct');

4. Tips

4.1. Using Jetpack Without A Wordpress.com Account

You can use many of the features of Jetpack without a wordpress.com account by enable development mode in your wp-config.php:

define( 'JETPACK_DEV_DEBUG', true);


CategoryMemberManual CategoryMemberManual

  1. It creates a file and then check that the UID is the same as the current process; at HCoop, this is not true since the file owner will be your daemon user which has a different UID. The owner UID check is pointless, and just makes our lives harder (1)

MemberManual/WebApplications/WordPress (last edited 2022-01-25 07:35:03 by JesseShumway)