Changes between Version 31 and Version 32 of OSLMigration

Author:

kuechlej (IP: 128.193.38.114)

Timestamp:

07/13/09 14:57:24 (4 months ago)

Comment:

--

OSLMigration

@@ -2 +2 @@
-The Open Source Lab environment is drastically different from our solution with Central Web Services. The largest problem we ran into was bugs that used a managed postgres cluster as oppose to running the server locally. It took a lot of time to understand which permissions were needed, since we normally use superuser access on the current local server.  
-
-Another difference was that the OSL
-
- bit, and change where things are located. These have been taken care of for the most part with symlinks
+The OSL also
+
+s well as change where '''things''' are located. These have been solved with symlinks for the most part
-
-== OSL Environment ==
-
-=== Apache ===
-
+-
-
-beaversource.oregonstate.edu vhost:
-
-=== Subversion ===
-do things like limit the size of commits, enforce permissions, and let Trac interact with commits. With hardened Gentoo, we ran into issues with grsec not letting use execute the chain of scripts for each hook because the absolute path to the interpreter wasn't included in the hook script(thusly relying on 'shebangs' to identify interpreters). In order to solve this problem, we first needed to ensure that the chain of hook scripts were all in a single language(purely for simplicity), and then had to append the path to that interpreter. Since the majority of our scripts were Python(all but one), we rewrote the one script in Python, and appended the path to the Python interpreter in each hook
+manage the size limits of commits, enforce permissions, and let Trac interact with commits. With hardened Gentoo, we ran into issues with grsec that wouln't let us execute the chain of scripts for each hook because the absolute path to the interpreter wasn't included in the hook script(thusly relying on 'shebangs' to identify interpreters). In order to solve this problem, we first needed to ensure that the chain of hook scripts were all in a single language (purely for simplicity), and then had to append the path to that interpreter. Since the majority of our scripts were Python (all but one), we rewrote '''the one''' script in Python, and appended the path to the Python interpreter in each hook 
-{{{
-#!/bin/bash
-}}}
-
- to ensure that all new projects have their hooks created properly, so we edited beaversource.py to append the path when hooks are
+ed to ensure that all new projects have their hooks created properly, so we edited beaversource.py to append the path when hooks were later
-
-=== Elgg ===
-Setting up Elgg is pretty straight forward, and didn't change much with the migration
-
- to do is check 
+Elgg didn't change much with the migration; the Elgg setup was pretty straightforward
+
+ed to do was check
-{{{
-$ cd /var/www/beaversource.oregonstate.edu
-}}}
-
-an now create the settings file. We do
+ould then create the settings file. We did
-{{{
-$ cp config-dist.php config.php
-}}}
-
-quite a bit
+significantly
-
-Elgg Configuration:
-A few notes on the Beaversource Elgg configuration:
- * We are using Postgres8, but the config still requires that we put 'postgres7'
-VERY IMPORTANT
+'''VERY IMPORTANT'''
-
-Apache Vhost:
- * Django 1.0 is installed and managed by the OSL.
-
-
+ed
-{{{
-$ cd /data/django/webmanagement
-}}}
-
-i
+wa
-{{{
-$ cp settings.py.dist settings.py
-}}}
-
-With your favorite text editor, open settings.py and edit the pertinent information
+You can edit this file with a text editor. Open settings.py and edit the pertinent information 
-
-One of the few differences that using WSGI causes effects the urls file. Since WSGI interprets the url we want to use(/request in this case) as the root mountpoint(/), its important to remove the 'request' from our urlconf. You can see this in the following diff:
-}}}
-
-The last thing to make sure the webmanagement Django project is working properly is SSO
+SSO is the last component to check that will verify that the webmanagement Django project is working properly
-
-I've included the sections of the Apache config and the WSGI script we use for Django.