Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/macinstall.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/macinstall.xml,v diff -u -r1.3.2.1 -r1.3.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/macinstall.xml 9 Dec 2003 09:54:05 -0000 1.3.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/macinstall.xml 18 Dec 2003 10:02:20 -0000 1.3.2.2 @@ -6,17 +6,38 @@ ]> -OpenACS Installation Guide for Mac OS X - There are several resources for installing on OS X. + OpenACS Installation Guide for Mac OS X + + Prerequisites + Install readline: + + + + Download readline from http://ftp.gnu.org/pub/gnu/readline/readline-4.3.tar.gz into /usr/local/src + + + Extract readline in /usr/local/src, configure, compile, and install: + su - root +cd /usr/local/src +tar xvfz readline-4.3.tar.gz +readline-4.3 +./configure +make +make install + + + Proceed with the Unix-like system instructions. OS X is incompatible with Oracle 8, and Oracle 9i on OSX is not yet verified for OpenACS. So continue with . Additional special steps for OS X are documented inline with the standard Unix-like instructions. + + + + Additional resources for installing on OS X. OpenACS on Mac OS X Quickstart An older forum thread - ($Id$) - Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml,v diff -u -r1.17.2.5 -r1.17.2.6 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml 15 Dec 2003 13:17:07 -0000 1.17.2.5 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml 18 Dec 2003 10:02:20 -0000 1.17.2.6 @@ -208,18 +208,18 @@ This is text that you will see and type in a command shell, including text you may have to change. It is followed by a list of just the commands, - which you can copy and paste. The command prompt varies by system; in the examples we use the form[nsadmin aolserver]$, where nsadmin is the current user and aolserver is the current directory. The root prompt is shown ending in # and all other prompts in $. + which you can copy and paste. The command prompt varies by system; in the examples we use the form[service0 aolserver]$, where service0 is the current user and aolserver is the current directory. The root prompt is shown ending in # and all other prompts in $. -[root root]# su - nsadmin -[nsadmin aolserver]$ svc -d /service/server1 -[nsadmin aolserver]$ dropdb server1 +[root root]# su - service0 +[service0 aolserver]$ svc -d /service/service0 +[service0 aolserver]$ dropdb service0 DROP DATABASE -[nsadmin aolserver]$ createdb server1 +[service0 aolserver]$ createdb service0 CREATE DATABASE -su - nsadmin -svc -d /service/server1 -dropdb server1 -createdb server1 +su - service0 +svc -d /service/service0 +dropdb service0 +createdb service0 Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/postgres.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/postgres.xml,v diff -u -r1.15.2.6 -r1.15.2.7 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/postgres.xml 15 Dec 2003 14:29:16 -0000 1.15.2.6 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/postgres.xml 18 Dec 2003 10:02:20 -0000 1.15.2.7 @@ -14,11 +14,16 @@ Skip this section if you will run only Oracle. - OpenACS &version; will run with PostgreSQL 7.2.x, 7.3.2, - 7.3.3, and 7.3.4. 7.3.4 is the recommended version of PostgreSQL. + OpenACS &version; will run with PostgreSQL 7.2.x, 7.3.2, 7.3.3, and 7.3.4. 7.3.4 is the recommended version of PostgreSQL. PostgreSQL 7.4 has been verified. + + Mac OS X + If you are running Mac OS X prior to 10.3, you should be able to install and use PostGreSQL 7.2.x or 7.3.x. Mac OS X 10.3 requires PostGreSQL 7.4. + + + Debian @@ -99,18 +104,33 @@ mkdir -p /usr/local/pgsql chown -R postgres.web /usr/local/pgsql /usr/local/src/postgresql-7.3.4 chmod 750 /usr/local/pgsql - + + + Mac OS X: Do instead: + sudo niutil -create / /groups/web +sudo niutil - list / /groups + The second command returns a list of groups. The last entry should include the gid of the group web, which you will need in the next sequence: + sudo niutil -create / /users/postgres +sudo niutil -createprop / /users/postgres gid web's gid_number +sudo niutil -createprop / /users/postgres home /usr/local/pgsql +sudo niutil -createprop / /users/postgres shell /bin/bash +mkdir -p /usr/local/pgsql +chown -R postgres:web /usr/local/pgsql /usr/local/src/postgresql-7.4 +chmod 750 /usr/local/pgsql + + + Set up postgres's environment variables They are necessary for the executable to find its supporting - libraries. For convenience, we'll simply append the necessary - lines to the postgres shell config file. + libraries. Put the following lines into the postgres user's environment. - [root src]# echo "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib" >> ~postgres/.bashrc -[root src]# echo "export PATH=$PATH:/usr/local/pgsql/bin" >> ~postgres/.bashrc -echo "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib" >> ~postgres/.bashrc -echo "export PATH=$PATH:/usr/local/pgsql/bin" >> ~postgres/.bashrc + [root src]# su - postgres +[postgres ~] emacs ~postgres/.bashrc + Paste these lines into .bashrc: +export PATH=$PATH:/usr/local/pgsql/bin +export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib Test this by logging in as postgres and checking the paths; you should see /usr/local/pgsql/bin @@ -388,6 +408,18 @@ Starting PostgreSQL: ok root:~ # + + Mac OS X: + + + Install the startup script: + cd /Library/StartupItems/ +tar xfz /var/lib/aolserver/service0/packages/acs-core-docs/www/files/osx-postgres-startup-item.tgz + + + + + Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml,v diff -u -r1.6.2.8 -r1.6.2.9 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml 16 Dec 2003 13:58:43 -0000 1.6.2.8 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml 18 Dec 2003 10:02:20 -0000 1.6.2.9 @@ -166,19 +166,67 @@ Upgrading OpenACS 4.6.3 to 5.0 - Current working notes in Forum OpenACS Development: 4.6.3 upgrade to 5-HEAD: final results. + +pg_dump mydb > mydb.dmp + +If you are also upgrading from postgresql 7.2 to postgresql 7.3: +From openacs 5.0 + +/openacs-5/bin/pg_7.2to7.3_upgrade_helper.pl mydb.dmp mydb-new.dmp /path/to/openacs-4-install + + * Reload mydb-new.dmp into postgresql 7.3. + * psql -f /openacs-5/packages/acs-kernel/sql/postgresql/postgresql.sql mydb + * Load acs-kernel sql upgrade scripts from the previous openacs version. Be sure to load 5.0d* scripts before 5.0.0b* scripts. + * Load acs-service-contract sql upgrade scripts + * Load acs-authentication data model + psql -f openacs-5/packages/acs-authentication/sql/postgresql/acs-authentication-create.sql mydb + * Load acs-lang data model + psql -f openacs-5/packages/acs-lang/sql/postgresql/acs-lang-create.sql mydb + +Next create in openacs-5/tcl/ zzz-postload.tcl containing + +if {![apm_package_installed_p acs-lang]} { + + apm_package_install -enable -mount_path acs-lang [acs_root_dir]/packages/acs-lang/acs-lang.info + + lang::catalog::import -locales [list "en_US"] + +} + + +if {![apm_package_installed_p acs-authentication]} { + + apm_package_install -enable [acs_root_dir]/packages/acs-authentication/acs-authentication.info + + apm_parameter_register "UsePasswordWidgetForUsername" \ + "Should we hide what the user types in the username + field, the way we do with the password field? Set + this to 1 if you are us ing sensitive information + such as social security number for username." \ + acs-kernel 0 number \ + security 1 1 + parameter::set_value -package_id [ad_acs_kernel_id] -parameter UsePasswordWidgetForUsername -value 0 + +} + +Cross fingers. + +If you can login, visit /acs-admin/apm and upgrade acs-kernel, acs-service-contract and uncheck the data model scripts. Restart. If everything is still working, make another backup of the database. Then upgrade the rest of your packages through the APM. + + +See also this forum post: Forum OpenACS Development: 4.6.3 upgrade to 5-HEAD: final results. Upgrading the OpenACS files OpenACS is distributed as a collection of files, available as one big tarball, via CVS, and via automatic download from within the APM. Upgrades work by first changing the file system (via any of the previous methods), and then using the APM to scan the file system, find upgrade scripts, and execute them. This section describes how to upgrade the file system. Starting with OpenACS 5.0, this section can generally be skipped because the OpenACS APM can directly download new files from the openacs.org repository. - If you are using CVS, you will unpack the OpenACS 4.6 tarball into a working directory and then import that directory into cvs. If you have changed files in the core packages, cvs will attempt to merge your changes. You may have to manually merge some conflicts. When that's finished, you can update your normal development checkout directory and the new files will appear. If you aren't using CVS, you can unpack the tarball on top of your existing tree, but any customizations you've made to the kernel or core packages will be erased. + Many OpenACS site developers operate their own CVS repository to keep track of changes from the release OpenACS code. This part describes how to import the latest OpenACS version into your own repository. If you are using CVS, you will unpack the OpenACS 4.6 tarball into a working directory and then import that directory into cvs. If you have changed files in the core packages, cvs will attempt to merge your changes. You may have to manually merge some conflicts. When that's finished, you can update your normal development checkout directory and the new files will appear. If you aren't using CVS, you can unpack the tarball on top of your existing tree, but any customizations you've made to the kernel or core packages will be erased. - Upgrading files without CVS + Upgrading files for a site which is not in a CVS repository Unpack the tarball into a new directory and copy its contents on top of your working directory. [root root]# su - service0 @@ -195,7 +243,7 @@ - Upgrading files with CVS + Upgrading files for a site which is in a CVS repository