|
Size: 1672
Comment:
|
Size: 2883
Comment: I am installing wordpress, so ... let's get this finished
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| WORK IN PROGRESS BY FrankBynum, please feel free to contribute and edit but please do not use quite yet. | ## page was renamed from MemberManual/ServingWebsites/WordPress {{{#!wiki warning This is a work in progress and following this guide will probably result in a broken installation. Do not use! }}} |
| Line 7: | Line 12: |
| 1. Navigate to the directory you where want to host Wordpress. This can be anywhere in your home directory, but it is usually within your public_html directory. | <<TableOfContents>> |
| Line 9: | Line 14: |
| 2. Now we will set the initial file permissions for the Wordpress root directory. In a moment, we will be using Subversion to create several folders and files. In AFS, new folders inherit the permissions of the parent folder. So by setting file permissions early, we can save ourselves some work later. | == Request Firewall Rules == |
| Line 11: | Line 16: |
| Navigate to the directory where you will install Wordpress and execute the following: | See FirewallRules |
| Line 13: | Line 18: |
| ''fsr setacl . system:anyuser none'' | If you want to use services like akismet or the wordpress plugin registry from the interface itself, you will need to [[https://members.hcoop.net/portal/sec|request firewall rules]] on the web server to contact those services. Something like: `$YOU Client 80,443 rest.akismet.com wordpress.org` is usually sufficient. |
| Line 15: | Line 20: |
| ''fsr sa . $USER.daemon rlk'' | == Get the Source == |
| Line 17: | Line 22: |
| 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 priviliges that the server software-- Apache and PHP mainly-- have over the directory to just reading, listing files, and executing code. | If you have the [[MemberManual/TransferringFiles/OpenAFS|OpenAFS client configured]], you can set up Wordpress on your local system for the most part. If you are performing the steps on the shell server, you will need to request FirewallRules to access http and subversion. |
| Line 19: | Line 24: |
| X. Follow the [[http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion | instructions for installing WordPress using Subversion]]. | * Navigate to the directory you where want to host Wordpress. This can be anywhere in your home directory, but it is usually within your public_html directory. * Now we will set the initial file permissions for the Wordpress root directory. In a moment, we will be using Subversion to create several folders and files. In AFS, new folders inherit the permissions of the parent folder. So by setting file permissions early, we can save ourselves some work later. * Navigate to the directory where you will install Wordpress and execute the following: |
| Line 21: | Line 28: |
| {{{ fsr setacl . system:anyuser none fsr sa . $USER.daemon rlk }}} |
|
| Line 22: | Line 33: |
| 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-- Apache and PHP mainly-- have over the directory to just reading, listing files, and executing code. * Follow the [[http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion | instructions for installing WordPress using Subversion]]. You will probably want to [[http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion#Tracking_Stable_Versions|track the stable version]] rather than trunk. {{{ svn co http://core.svn.wordpress.org/tags/$VERSION . }}} * You need to allow your daemon user to write to a few directories in order to use the plugin manager and upload files. {{{ |
|
| Line 23: | Line 45: |
| fsr sa themes/ USER.daemon rlkw | fsr sa themes/ $USER.daemon rlkw |
| Line 25: | Line 47: |
| fs sa uploads frank.daemon rlkwid | fs sa uploads $USER.daemon rlkwid }}} ---- CategoryMemberManual CategoryNeedsWork |
This is a work in progress and following this guide will probably result in a broken installation. Do not use!
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.
Contents
1. Request Firewall Rules
See FirewallRules
If you want to use services like akismet or the wordpress plugin registry from the interface itself, you will need to request firewall rules on the web server to contact those services. Something like: $YOU Client 80,443 rest.akismet.com wordpress.org is usually sufficient.
2. Get the Source
If you have the OpenAFS client configured, you can set up Wordpress on your local system for the most part. If you are performing the steps on the shell server, you will need to request FirewallRules to access http and subversion.
- Navigate to the directory you where want to host Wordpress. This can be anywhere in your home directory, but it is usually within your public_html directory.
- Now we will set the initial file permissions for the Wordpress root directory. In a moment, we will be using Subversion to create several folders and files. In AFS, new folders inherit the permissions of the parent folder. So by setting file permissions early, we can save ourselves some work later.
- Navigate to the directory where you will install Wordpress and execute the following:
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-- Apache and PHP mainly-- have over the directory to just reading, listing files, and executing code.
Follow the instructions for installing WordPress using Subversion. You will probably want to track the stable version rather than trunk.
svn co http://core.svn.wordpress.org/tags/$VERSION .
- You need to allow your daemon user to write to a few directories in order to use the plugin manager and upload files.
cd wp-content/ fsr sa themes/ $USER.daemon rlkw mkdir uploads fs sa uploads $USER.daemon rlkwid