Home
The Toolkit for Online Communities
17619 Community Members, 1 member online, 2635 visitors today
Log In Register
OpenACS Home : xowiki : Weblog
Search · Index
Previous Month November 2014
Sun Mon Tue Wed Thu Fri Sat
26 27 28 29 30 31 1
2 3 4 5 6 7 8
9 10 11 12 13 (3) 14 15
16 17 18 19 20 21 22
23 24 25 (1) 26 27 (1) 28 29
30 1 2 3 4 5 6

Popular tags

ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bugtracker , COMET , cvs , debian , emacs , fedora , FreeBSD , hstore , includelets , install , installation , installers , javascript , libthread , linux , monitoring , naviserver , nginx , nx , OmniOS , oracle , osx , patches , performance

No registered users in community xowiki
in last 30 minutes

Contributors

OpenACS.org

Weblog

Showing 1 - 10 of 821 Postings (summary)

OpenACS compatibility matrix

Created by Joel Aufrecht, last modified by Gustaf Neumann 07:55 AM, Wednesday

OpenACS requires, at a minimum, an operating system, database, and webserver to work. Many additional programs, such as a build environment, Mail Transport Agent, and source control system, are also needed for a fully effective installation.

Table 2.2. Version Compatibility Matrix

OpenACS Version 3.2.5 4.5 4.6 4.6.1 4.6.2 4.6.3 5.0 5.1 5.2 (core)
5.3 (core)
5.4 (core)
5.5 (core)
5.6 (core)
5.7 (core)
5.8 (core)
AOLserver 3 Yes No
3.3+ad13 Maybe Yes No
3.3oacs1 Maybe Yes No
3.4.4 No
3.4.4oacs1 Maybe Yes No
3.5.5 Maybe Yes No
4.0 Maybe Yes
4.5 No Yes
Naviserver 4.99.4 - No Maybe Yes
Tcl 8.4 Yes No
8.5.4 - Maybe Yes
PostgreSQL 7.0 Yes No
7.2 Maybe Yes No
7.3.2 - 7.3.x No Yes No
7.4 No Yes No
8.0 No Maybe Yes Maybe
8.1 No Yes Maybe
8.2 No tar: no, CVS: Yes Yes Maybe
8.3 No Yes Maybe
8.4 No Yes
9.0 - 9.4 No Yes
Oracle 8.1.6 Maybe Yes Maybe
8.1.7 Maybe Yes Maybe
9i No Yes Maybe
10g No Yes Maybe
11g No Maybe

The value in the cells correspond to the last version of that release, and not necessarily to all minor releases. Empty cells denote an unknown status.

Spreadsheet

Created by Benjamin Brink, last modified by Gustaf Neumann 14 Nov 2014, at 07:58 PM

For the latest updates to this readme file, see: http://openacs.org/xowiki/spreadsheet

Package specification Summary for package spreadsheet

Summary: Spreadsheet package for collaboratively building and managing spreadsheets.
Description: Spreadsheet package provides users with some spreadsheet-like functionality, such as ability to perform basic queries on package tables for generating customized reports. Smallest spreadsheet can be 1 by 1.
Maturity: New Submission or Maturity Unknown
This package depends on: None
Packages that depend on spreadsheet: accounts-finance


Bug Tracker Summary for package spreadsheet

There is no package with the name "spreadsheet" known to bug-tracker.



Code Metrics Summary for package spreadsheet

# Tcl Procs 42
# Tcl Lines 3060
# Automated Tests 0
# Stored Procedures PG: 0 ORA: 0
# SQL Lines PG: 0 ORA: 0
# ADP pages 3
# ADP lines 34
# Include pages (spreadsheet/lib/) 1
# Documentation pages 2
# Documentation lines 68
Source Not installed
 

The lastest version of the code is available at the development site: http://github.com/tekbasse/spreadsheet

introduction

Spreadsheet provides procedures for building and using tables and spreadsheets in OpenACS. It is an OpenACS package that allows convenient building and interpreting of web-based sheets via tcl in a web page.

Standard spreadsheets are not yet supported.

license

Copyright (c) 2013 Benjamin Brink po box 20, Marylhurst, OR 97036-0020 usa email: kappa@dekka.com

Spreadsheet is open source and published under the GNU General Public License, consistent with the OpenACS system:http://www.gnu.org/licenses/gpl.html A local copy is available at spreadsheet/LICENSE.html

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

features

Integrates well with Q-Forms or any web-based form processing.

Tables can be represented as text, where each line is a row, and each cell is separated by a common or specified delimiter.

Can manipulate Tcl list of lists for easy generation of reports.

There are procedures for importing, rotating, and exporting tables in various formats.


Q-Forms

Created by Benjamin Brink, last modified by Gustaf Neumann 14 Nov 2014, at 07:57 PM

For the latest updates to this readme file, see: http://openacs.org/xowiki/q-forms

Package specification Summary for package q-forms

Summary: Provides code for building forms dynamically in tcl
Description: Provides qf_* form bulding and interpreting procedures, especially designed for building forms dynamically.
Maturity: Immature
This package depends on: None
Packages that depend on q-forms: accounts-finance


Bug Tracker Summary for package q-forms

There is no package with the name "q-forms" known to bug-tracker.



Code Metrics Summary for package q-forms

# Tcl Procs 36
# Tcl Lines 2453
# Automated Tests 0
# Stored Procedures PG: 0 ORA: 0
# SQL Lines PG: 0 ORA: 0
# ADP pages 0
# ADP lines 0
# Include pages (q-forms/lib/) 0
# Documentation pages 2
# Documentation lines 80
Source Not installed
 

The latests version of the code is available at the development site: http://github.com/tekbasse/q-forms

introduction

Q-Forms provides procedures for building forms dynamically in OpenACS. It is an OpenACS service package that allows convenient building and interpreting of web-based forms via tcl in a web page.

(jiml) isn't there already a form builder? via tcl, and integrated well with templating system. Does q-forms use the existing form builder? If not, then we have two incompatible versions of this functionality.

jiml, current form building techniques can be "tricky"[1], whereas Q-Forms has an intuitive interface. You say "Incompatible"? Use one or the other form building process. With Q-wiki, there are now at least four different wiki-like packages for OpenACS. They work with each other within the templating system. Why would form building resources be expected to share package resources? (tekbasse)

Q-Forms procedures begin with qf_* and parallel form html tags with many automatic defaults that remove the tedious nature of building forms via html or an alternate form building context, such as OpenACS form builder, ad_form or acs-templating.

(jiml) could someone provide an example showing how ad_form or the original template::form and friends are unsuitable? 

A lot of people use these things including myself. I read the existing documentation, and then understood how to do it.

^ Good for you, jiml. You don't have to use Q-Forms. (tekbasse)

In particular, ad_form offers easy-to-build forms which provide create and edit functionality as it has parameters that accept sql queries which create, access and store as well as provide conversion where necessary to acs_objects whose type match the form. ( Really easy? see: http://openacs.org/wiki/ad_form -tekbasse) But I digress:

What's wrong with the existing implementation and what has you wanting to take the extreme action of adding an incompatible replacement? How can I support you in creating something that -is- compatible? (jiml)

jiml, Once you learned how to create a form in html, how much time did you spend trying to create a form with ad_form or formbuilder?  If it's more than 10 minutes, Q-Forms would be faster and has more flexibility without having to learn more to tweak a special context.

The simplicity of form creation in the context of basic tcl programming techniques makes the learning curve for Q-Forms very low compared to ad_form and formbuilder. (tekbasse)

jiml, you ask "..what has you wanting to take the extreme action of adding an incompatible replacement? " I am writing web apps that regularly include spreadsheets, tables, and other kinds of data which require any form building API to be flexible while retaining a minimum amount of overhead and meeting requirements expected of ecommerce transactions. Can you show me in ad_form API how to pass a table with a flexible size and that allows data to include negative and decimal numbers (or user_names starting with a dash..) and also dates/time values and where each cell format can be customized?  ;-)  -tekbasse

license

Copyright (c) 2013 Benjamin Brink po box 20, Marylhurst, OR 97036-0020 usa email: kappa@dekka.com

Q-Forms is open source and published under the GNU General Public License, consistent with the OpenACS system:http://www.gnu.org/licenses/gpl.html A local copy is available at q-forms/LICENSE.html

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

features

Low learning-curve. Uses tcl context. Procedures match tags. List friendly.

Built in API defaults. Takes less keystrokes to build a form than typing manually.

Can built multiple forms concurently using Tcl file terminology.

No limitations to building dynamic forms with specialized inputs.

Form values are retrieved as an array named by the programmer.

Form values are automatically quoted, a requirement of secure input handling.

Multiple values of same key can be combined as a list (instead of producing a form post error).

html can be inserted in any form at any point during the build.

No UI javascript is used. Technologies with limited UI or cpu power can use it.

Integrates with acs-templating features.

Accounts Finance

Created by OpenACS community, last modified by Gustaf Neumann 14 Nov 2014, at 07:39 PM

Package specification Summary for package accounts-finance

Summary: Finance package provides limited set of tools for long-term debts, fixed assets, forecasting.
Description: Finance package provides some tools for long-term debts, fixed assets, capital, stock holding, dividends, forecasting and reporting. Integrates with general-ledger etc.
Maturity: Immature
This package depends on: acs-datetime q-forms spreadsheet
Packages that depend on accounts-finance: None

Bug Tracker Summary for package accounts-finance

There is no package with the name "accounts-finance" known to bug-tracker.

Code Metrics Summary for package accounts-finance

# Tcl Procs 84
# Tcl Lines 9574
# Automated Tests 7
# Stored Procedures PG: 0 ORA: 0
# SQL Lines PG: 0 ORA: 0
# ADP pages 5
# ADP lines 303
# Include pages (accounts-finance/lib/) 7
# Documentation pages 20
# Documentation lines 739
Source Not installed

Status

pre-release

Introduction

Part of the ecommerce-g2 project

Feature requests

add requests here

News

Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 21 Oct 2014, at 09:07 AM

Package specification Summary for package news

Summary: Used for announcements and news items.
Description: News publication tool. Publication of plain text or html news items with support for scheduled publication and commentability.
Maturity: Mature
This package depends on: acs-content-repository acs-datetime acs-kernel general-comments notifications rss-support
Packages that depend on news: news-includelet news-portlet
Error in includelet '{{adp /www/templates/bug-tracker {package_key news}}}' of page en:news:
Nesting of includelets is to deep
Error in includelet '{{adp /www/templates/metrics {package_key news}}}' of page en:news:
Nesting of includelets is to deep

Wiki

Created by gustaf neumann, last modified by Gustaf Neumann 10 Oct 2014, at 02:28 PM

Welcome to the OpenACS Wiki!

This is the OpenACS Wiki system, built with the xowiki package. This wiki contains user documentation, how-tos, and tips and tricks related to OpenACS. It also serves as a collaboration area for OpenACS contributors.

Quick Links:

OpenACS Handbook: openacs-handbook
OpenACS Packages
: packages

Recent Wiki Page Edits:

Error in includelet '{{categories-recent -title "Recent Entries by Categories" -max_entries 25 -decoration plain -pretty_age 1}}' of page en:index:
Nesting of includelets is to deep


XoWiki

Created by Gustaf Neumann, last modified by Antonio Pisano 27 Sep 2014, at 12:20 PM

XoWiki is a wiki implementation for OpenACS  implemented based on xotcl-core. Instead of trying to implement the full set of wiki markup commands in systems like MediaWiki, XoWiki is based on a rich text editor and focuses more on integration with OpenACS (e.g. categories, general comments, adp-includes, ad-substitution of template variables). XoWiki combines aspects of wikis (ease of page-creation) with aspects of a content management system (revisions, reusable content, multiple languages, page templates).

XoWiki provides functionalities of enterprise wiki systems (such as combining structured with unstructured information, providing security policies, etc.). XoWiki is reused in several other packages such as XoWiki Content flow, S5 or  the Learning Content Tool.

Documentation:


Error in includelet '{{adp /www/templates/info-file {package_key xowiki}}}' of page en:xowiki:
Nesting of includelets is to deep

Error in includelet '{{adp /www/templates/bug-tracker {package_key xowiki}}}' of page en:xowiki:
Nesting of includelets is to deep

Error in includelet '{{adp /www/templates/metrics {package_key xowiki}}}' of page en:xowiki:
Nesting of includelets is to deep


XOTcl Core

Created by Gustaf Neumann, last modified by Gustaf Neumann 16 Sep 2014, at 10:43 AM

What is xotcl-core

xotcl-core is an OpenACS package, which provides base functionality for OpenACS applications using XOTcl. The xotcl-core package is used by several other OpenACS packages such as the XOTcl request monitor, XoWiki, XoWiki Content Flow, S5 or the Learning Content Tool.

Install xotcl-core

First, get xotcl-core from the OpenACS repository:

cd /tmp
cvs -d:pserver:anonymous@cvs.openacs.org:/cvsroot co openacs-4/packages/xotcl-core

Move xotcl-core to the directory, where your OpenACS packages are stored. We assume, this directory is /usr/local/openacs-4/packages

mv /tmp/openacs-4/packages/xotcl-core /usr/local/openacs-4/packages
 Next, go to acs-admin/apm (http://YOURSERVER/acs-admin/apm/), choose "install-packages" and install XOTcl Core. Finally, restart the server.
svc -t /service/${yourservice}

Now you can browse  http://YOURSERVER/xotcl

Functionality of xotcl-core

xotcl-core defines several classes for

  • library dependencies
  • package management
  • debugging
  • security and policy management
  • HTTP client and server functionality
  • Object Relational Database Interface
  • ical formatting
  • cluster management
  • chat handlers

and several utilities.

Tutorial xotcl-core

 See http://alice.wu-wien.ac.at:8000/s5-xotcl-core-tutorial/slides 


Code metrics and Package Description

Error in includelet '{{adp /www/templates/info-file {package_key xotcl-core}}}' of page en:xotcl-core:
Nesting of includelets is to deep

Error in includelet '{{adp /www/templates/bug-tracker {package_key xotcl-core}}}' of page en:xotcl-core:
Nesting of includelets is to deep

Error in includelet '{{adp /www/templates/metrics {package_key xotcl-core}}}' of page en:xotcl-core:
Nesting of includelets is to deep
nbsp;

The OpenACS package xotcl-core requires in versions of OpenACS before 5.3 the following patches for the documentation procs and the bootstrap installer:

cd /tmp
wget http://media.wu-wien.ac.at/download/acs-api-documentation-procs.patch
wget http://media.wu-wien.ac.at/download/acs-bootstrap-installer.patch
To apply these patches, go to the directory, where the OpenACS packages are stored. We assume, this directory is /usr/local/openacs-4/packages. 

cd /usr/local/openacs-4/packages
 patch -p 0 < /tmp/acs-api-documentation-procs.patch
 patch -p 0 < /tmp/acs-bootstrap-installer.patch
Both patches do not harm in case XOTcl is not installed. Now reload these packages or restart the aolserver.

Installing OpenACS on FreeBSD with ports

Created by Gustaf Neumann, last modified by Gustaf Neumann 04 Sep 2014, at 07:47 PM

NEW:  For the impatient users there is a quick-and-dirty install guide for FreeBSD

OpenACS and .LRN are included in the current FreeBSD ports tree.
The ports are tested with FreeBSD production version 6.2-RELEASE, old stable 5.5-RELEASE and the development branch 7-CURRENT.

Installation requirements:

  1. FreeBSD operating system with root access rights.
  2. Installed and updated FreeBSD Ports Collection (for updating see Appendix A below)
    (alternative: installing from packages, see Appendix B)

To install OpenACS or .LRN from the FreeBSD ports tree, follow the instructions below.

1. Installing and configuring PostgreSQL

NOTICE: If you have a PostgreSQL server installed and running, skip to Section 2.

If you desire to use a local PostgreSQL server (most users do), install the server first.
We recommend using PostgreSQL version 8.2 from the databases/postgresql82-server port

# cd /usr/ports/databases/postgresql82-server # make install clean

NOTICE: As an alternative, you may install PostgreSQL server from a binary package. See Appendix B below

The plperl language is required for OpenACS/.LRN. This can be installed from the ports with the following commands:

# cd /usr/ports/databases/p5-postgresql-plperl # make install clean

To install the OpenACS/.LRN database, your PostgreSQL server must be running.
You need to enable it in your /etc/rc.conf (or /etc/rc.conf.local) by adding the following line:

postgresql_enable="YES"

After installing the PostgreSQL server, you have to initialize your data store:

# /usr/local/etc/rc.d/postgresql initdb

To start the PostgreSQL server, issue the following command:

# /usr/local/etc/rc.d/postgresql start

You can check if the server is up and running with:

# /usr/local/etc/rc.d/postgresql status

2. Installing OpenACS / .LRN

2.1 Installing the OpenACS or .LRN port 

OpenACS can be installed directly from the FreeBSD ports tree, www/openacs:

# cd /usr/ports/www/openacs
# make install clean

.LRN installation, www/openacs-dotlrn:

# cd /usr/ports/www/openacs-dotlrn
# make install clean

NOTICE: If you want to make changes to the default configuration, the AOLserver configuration files for OpenACS/.LRN files are located at:
/usr/local/openacs/etc/openacs-config.tcl
/usr/local/dotlrn/etc/dotlrn-config.tcl

NOTICE: If you installed both OpenACS and .LRN ports, you have to change the default port of one of the installations. See the configuration files in the previous notice.

2.2 Creating the OpenACS/.LRN database 

For this step, you require an installed and running PostgreSQL server (see Section 1) and installed OpenACS/.LRN (see Section 2.1)

First we need to adjust the PostgreSQL configuration (this applies for server versions 8.1.x and higher):

# /usr/local/share/doc/openacs/adjust_pgsql_conf.sh

or if .LRN was installed: 

# /usr/local/share/doc/dotlrn/adjust_pgsql_conf.sh

NOTICE: You can adjust the configuration manually (standard location: /usr/local/pgsql/data/postgresql.conf)
Please see en:How_to_install_in_Postgres_8.x.

The PostgreSQL server needs to be restarted after changing the configuration:

# /usr/local/etc/rc.d/postgresql restart

Next, we can create a default OpenACS database by running the following script:

# /usr/local/share/doc/openacs/create_sampledb.sh

To create a default .LRN database, run the following script:

# /usr/local/share/doc/dotlrn/create_sampledb.sh


2.3 Starting OpenACS/.LRN and finalizing installation 

To make use of the automatic startup script OpenACS/.LRN has to be enabled in /etc/rc.conf (or /etc/rc.conf.local):

openacs_enable="YES" 

or for .LRN:

dotlrn_enable="YES"

To start OpenACS, use the following command:

# /usr/local/etc/rc.d/openacs start

To start .LRN, use the following command:

# /usr/local/etc/rc.d/dotlrn start

Now you can login to your OpenACS/.LRN system and finalize the installation.
The default port is 8000. URL:

http://<your-ip>:<port>

After filling your e-mail address, password and other important information OpenACS/.LRN gets installed, but the server stops.
You have to start it again (see above).

 A. Updating the FreeBSD ports tree

To get the latest versions of the OpenACS, .LRN and other FreeBSD ports, it is recommended to update the FreeBSD ports tree on a regular basis. The easiest way to to perform this task is using the portsnap(8) command.

For documentation, refer to the following FreeBSD Handbook chapters:
Using the Ports Collection
Using Portsnap


B. Installing from binary packages

PostgreSQL, OpenACS, .LRN and all dependent ports may be installed from binary packages, too.
This installation can be performed from a submenu of FreeBSD's sysinstall(8) command: Configure/Packages

OpenACS and .LRN are located in subcategory www, PostgreSQL is in subcategory databases.


C. Contact information and bug reporting

Please send bug reports and feature suggestions to the port maintainer of OpenACS/.LRN FreeBSD ports:
Martin Matuska
<mm_at_FreeBSD_dot_org>

Installing OpenACS on FreeBSD

Created by OpenACS community, last modified by Gustaf Neumann 04 Sep 2014, at 07:33 PM

OpenACS and .LRN are available via FreeBSD ports. See en:openacs-system-install-freebsd-ports.

The following notes are useful if you decide to follow the OpenACS manual installation process using FreeBSD. These notes include points where a manual FreeBSD install differes from the slow, manual en:openacs-system-install.

The following information is pulled from: http://openacs.org/forums/message-view?message_id=312823 and http://openacs.org/forums/message-view?message_id=136910 and http://openacs.org/forums/message-view?message_id=312823

The OpenACS Reference Platform uses shell scripts written for bash, which is the standard Linux shell. If you are using a different shell, you will need to substitute your shell's conventions for setting environment variables when appropriate, and install bash to work with the scripts. Substitute fetch when the instructions suggest you use wget to download software.

Note that on most linux distributions, GNU Make is simply named make and there is no gmake, whereas on BSD distributions, make and gmake are different --use gmake.

Change the period separating user.group in chown commands to use a colon ":" instead. For example,

chown -R $OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME

becomes:

chown -R $OPENACS_SERVICE_NAME:$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME

Should you decide to install OpenACS from source using general en:openacs-system-install instructions, refer to these notes for changes:

Installing tdom

FreeBSD can use the standard tdom from ports when installing manually, without going the extra step of installing tdom within the aolserver src tree.

Installing en:postgresql

Creating postgres user

To set defaults for new users or special service users you may create, edit the file /etc/share/skel/dot.profile instead of /etc/profile

To create the user, we need to add more parameters to match what is expected from creating a user in linux.

[root src]# mkdir -p /usr/local/pgsql
[root src]# pw groupadd -n web
[root src]# pw useradd -n postgres -g web -d /usr/local/pgsql -s /bin/bash
[root src]# chown -R postgres:web /usr/local/pgsql /usr/local/src/postgresql-7.4.7
[root src]# chmod -R 750 /usr/local/pgsql
[root src]#
mkdir -p /usr/local/pgsql
pw groupadd -n web
pw useradd -n postgres -g web -d /usr/local/pgsql -s /bin/bash
chown -R postgres:web /usr/local/pgsql /usr/local/src/postgresql-7.4.7
chmod -R 750 /usr/local/pgsql

Set PostgreSQL to start on boot

[root ~]# cp /tmp/openacs-5.2.0d1/packages/acs-core-docs/www/files/postgresql.txt /usr/local/etc/rc.d/postgresql.sh
[root ~]# chown root:wheel /usr/local/etc/rc.d/postgresql.sh
[root ~]# chmod 755 /usr/local/etc/rc.d/postgresql.sh
[root ~]# 
cp /tmp/openacs-5.2.0d1/packages/acs-core-docs/www/files/postgresql.txt /usr/local/etc/rc.d/postgresql.sh
chown root:wheel /usr/local/etc/rc.d/postgresql.sh
chmod 755 /usr/local/etc/rc.d/postgresql.sh

Test the script

[root ~]# /usr/local/etc/rc.d/postgresql.sh stop
Stopping PostgreSQL: ok
[root ~]# 

If PostgreSQL successfully stopped, then turn it back on because we'll use it later.

[root root]# /usr/local/etc/rc.d/postgresql.sh start
Starting PostgreSQL: ok
[root root]#
/usr/local/etc/rc.d/postgresql.sh start

PostgreSQL performance tuning

See man syctl, man 5 sysctl and man 5 loader.conf.

Installing Libthreads 2.6.5

cd /usr/local/src/aolserver/
fetch http://mesh.dl.sourceforge.net/sourceforge/tcl/thread2.6.5.tar.gz
tar xzpf thread2.6.5.tar.gz
cd thread2.6.5/unix
less ../README
../configure --help
../configure --enable-threads --prefix=/usr/local/aolserver --exec-prefix=/usr/local/aolserver --with-aolserver=/usr/local/aolserver --with-tcl=/usr/local/lib/tcl8.4-threads
gmake
gmake install

Creating users

We need to add more parameters to have user environments match the linux ones expected by the en:openacs-reference-platform.

Create users this way:

[root root]# mkdir -p /home/$OPENACS_SERVICE_NAME
[root root]# pw useradd -n $OPENACS_SERVICE_NAME -g web -d /home/$OPENACS_SERVICE_NAME -s /bin/bash
[root root]#
mkdir -p /home/$OPENACS_SERVICE_NAME
pw useradd -n $OPENACS_SERVICE_NAME -g web -d /home/$OPENACS_SERVICE_NAME -s /bin/bash

Next Page