Weblog

Install OpenACS distribution

Created by OpenACS community, last modified by Gustaf Neumann 11 Oct 2017, at 08:42 AM

You should have an OpenACS distribution downloaded and available at /var/lib/aolserver/$OPENACS_SERVICE_NAME, otherwise en:Get_the_Code.

Option 1: Use an automated script

A bash script is available to automate all of the steps for the rest of this section. It requires tclwebtest. The automated script can greatly accelerate the install process, but is very sensitive to the install environment. We recommend that you run the automated install and, if it does not work the first time, consider switching to a manual installation.

Get the install script from CVS. It is located within the main cvs tree, at /etc/install. Use anonymous CVS checkout to get that directory in the home directory of the service's dedicated user. We put it there so that it is not overwritten when we do the main CVS checkout to the target location.

[root root]# su - $OPENACS_SERVICE_NAME
[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ cvs -d :pserver:anonymous@cvs.openacs.org:/cvsroot co -d install openacs-4/etc/install
cvs server: Updating install
U install/README
U install/TODO
  ... many lines omitted ...
U install/tcl/twt-procs.tcl
U install/tcl/user-procs.tcl
[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ cd install
[$OPENACS_SERVICE_NAME install]$ emacs install.tcl

Edit the installation configuration file, /home/$OPENACS_SERVICE_NAME/install/install.tcl and update the site-specific values, such as the new service's IP address and name, which will be written into the new service's config.tcl file. If your system is different from the one described in the previous sections, check the file paths as well. Set do_checkout=yes to create a new OpenACS site directly from a CVS checkout, or =no if you have a fully configured site and just want to rebuild it (drop and recreate the database and repeat the installation). If you have followed a stock installation, the default configuration will work without changes and will install an OpenACS site at 127.0.0.1:8000.

Run the install script install.sh as root:

[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ exit 
[root root]# sh /home/$OPENACS_SERVICE_NAME/install/install.sh
/home/$OPENACS_SERVICE_NAME/install/install.sh: Starting installation with config_file 
/home/$OPENACS_SERVICE_NAME/install/install.tcl. Using serverroot=/var/lib/aolserver/
$OPENACS_SERVICE_NAME, server_url=http://0.0.0.0:8000, do_checkout=yes, do_install=yes, 
dotlrn=no, and database=postgres., use_daemontools=true
  ... many lines omitted ...
Tue Jan 27 11:50:59 CET 2004: Finished (re)installing /var/lib/aolserver/$OPENACS_SERVICE_NAME.
######################################################################
  New site URL: http://127.0.0.1:8000
admin email   : admin@yourserver.net
admin password: xxxx
######################################################################
[root root]#

If there are no errors, you can browse to the "Welcome" page of your server. Be sure to visit en:docs-admin for administration help and en:docs-dev-tutorial for tutorials.

Option 2: Install available distribution

Secure the directory so that only the owner can access it. Check the permissions by listing the directory.

[root root]# su - $OPENACS_SERVICE_NAME
[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ cd /var/lib/aolserver
[$OPENACS_SERVICE_NAME aolserver]$ tar xzf /var/tmp/openacs-5.2.0d1.tgz
[$OPENACS_SERVICE_NAME aolserver]$ mv openacs-5.2.0d1 $OPENACS_SERVICE_NAME
[$OPENACS_SERVICE_NAME aolserver]$ chmod -R 775 $OPENACS_SERVICE_NAME
[$OPENACS_SERVICE_NAME aolserver]$ chown -R $OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME
[$OPENACS_SERVICE_NAME aolserver]$ ls -al
total 3
drwxrwx---    3 root     web          1024 Mar 29 16:41 .
drwxr-xr-x   25 root     root         1024 Mar 29 16:24 ..
drwx------    7 $OPENACS_SERVICE_NAME web          1024 Jan  6 14:36 $OPENACS_SERVICE_NAME
[$OPENACS_SERVICE_NAME aolserver]$ exit
logout
[root root]#
su - $OPENACS_SERVICE_NAME
cd /var/lib/aolserver
tar xzf /var/tmp/openacs-5.2.0d1.tgz
mv openacs-5.2.0d1 $OPENACS_SERVICE_NAME
chmod -R 755 $OPENACS_SERVICE_NAME
chown -R $OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME
exit

Prepare the database

Prepare Oracle for OpenACS. If you won't be using Oracle, skip to Prepare PostgreSQL for an OpenACS Service

You should be sure that your user account (e.g. $OPENACS_SERVICE_NAME) is in the dba group.

1. Verify membership by typing groups when you login:

   [$OPENACS_SERVICE_NAME ~]$ groups
   dba web

   If you do not see these groups, take the following action:

   [$OPENACS_SERVICE_NAME ~]$ su -
   Password: ************
   [root ~]# adduser $OPENACS_SERVICE_NAME dba

   If you get an error about an undefined group, then add that group manually:

   [root ~]# groupadd dba
   [root ~]# groupadd web

   Make sure to logout as root when you are finished with this step and log back in as your regular user.

2. Connect to Oracle using svrmgrl and login:

   [$OPENACS_SERVICE_NAME ~]$ svrmgrl
   SVRMGR> connect internal
   Connected.

    

3. Determine where the system tablespaces are stored:

   SVRMGR> select file_name from dba_data_files;

   Example results:

   /ora8/m01/app/oracle/oradata/ora8/system01.dbf
   /ora8/m01/app/oracle/oradata/ora8/tools01.dbf
   /ora8/m01/app/oracle/oradata/ora8/rbs01.dbf
   /ora8/m01/app/oracle/oradata/ora8/temp01.dbf
   /ora8/m01/app/oracle/oradata/ora8/users01.dbf
   /ora8/m01/app/oracle/oradata/ora8/indx01.dbf
   /ora8/m01/app/oracle/oradata/ora8/drsys01.dbf

    

4. Using the above output, you should determine where to store your tablespace. As a general rule, you'll want to store your tablespace on a mount point under the /ora8 directory that is separate from the Oracle system data files. By default, the Oracle system is on m01, so we will use m02. This enables your Oracle system and database files to be on separate disks for optimized performance. For more information on such a configuration, see Chapter 12 of Philip's book. For this example, we'll use /ora8/m02/oradata/ora8/.

5. Create the directory for the datafile; to do this, exit from svrmgrl and login as root for this step:

   SVRMGR> exit
   [$OPENACS_SERVICE_NAME ~]$ su -
   Password: ************
   [root ~]# mkdir -p /ora8/m02/oradata/ora8/
   [root ~]# chown $OPENACS_SERVICE_NAME:web /ora8/m02/oradata/ora8
   [root ~]# chmod 775 /ora8/m02/oradata/ora8
   [root ~]# exit
   [$OPENACS_SERVICE_NAME ~]$

6. Create a tablespace for the service. It is important that the tablespace can autoextend. This allows the tablespace's storage capacity to grow as the size of the data grows. We set the pctincrease to be a very low value so that our extents won't grow geometrically. We do not set it to 0 at the tablespace level because this would affect Oracle's ability to automatically coalesce free space in the tablespace.

   [$OPENACS_SERVICE_NAME ~]$ svrmgrl
   SVRMGR> connect internal;
   SVRMGR> create tablespace $OPENACS_SERVICE_NAME
         datafile '/ora8/m02/oradata/ora8/$OPENACS_SERVICE_NAME01.dbf' 
         size 50M 
         autoextend on 
         next 10M
         maxsize 300M
         extent management local
         uniform size 32K;

7. Create a database user for this service. Give the user access to the tablespace and rights to connect. We'll use $OPENACS_SERVICE_NAMEpassword as our password.

   Write down what you specify as service_name (i.e. $OPENACS_SERVICE_NAME) and database_password (i.e. $OPENACS_SERVICE_NAMEpassword). You will need this information for configuring exports and AOLserver.

   SVRMGR> create user $OPENACS_SERVICE_NAME identified by $OPENACS_SERVICE_NAMEpassword default tablespace $OPENACS_SERVICE_NAME
       temporary tablespace temp quota unlimited on $OPENACS_SERVICE_NAME;
   SVRMGR> grant connect, resource, ctxapp, javasyspriv, query rewrite, create view, create synonym to $OPENACS_SERVICE_NAME;
   SVRMGR> revoke unlimited tablespace from $OPENACS_SERVICE_NAME;
   SVRMGR> alter user $OPENACS_SERVICE_NAME quota unlimited on $OPENACS_SERVICE_NAME;
   SVRMGR> exit;

   Your table space is now ready. In case you are trying to delete a previous OpenACS installation, consult these commands in the section called “Deleting a tablespace” below.

8. Make sure that you can login to Oracle using your service_name account:

   [$OPENACS_SERVICE_NAME ~]$ sqlplus $OPENACS_SERVICE_NAME/$OPENACS_SERVICE_NAMEpassword
   SQL> select sysdate from dual;
   SYSDATE
   ----------
   2001-12-20
   SQL> exit;

   You should see today's date in a format 'YYYY-MM-DD.' If you can't login, try redoing step 1 again. If the date is in the wrong format, make sure you followed the steps outlined in the section called “Troubleshooting Oracle Dates”

Prepare PostgreSQL for an OpenACS Service.

• PostgreSQL:

  Create a user in the database matching the service name. With default PostgreSQL authentication, a system user connecting locally automatically authenticates as the postgres user of the same name, if one exists. We currently use postgres "super-users" for everything, which means that anyone with access to any of the openacs system accounts on a machine has full access to all postgresql databases on that machine.

  [root root]# su - postgres
  [postgres pgsql]$ createuser -a -d $OPENACS_SERVICE_NAME
  CREATE USER
  [postgres pgsql]$ exit
  logout
  [root root]#

• Create a database with the same name as our service name, $OPENACS_SERVICE_NAME.

  [root root]# su - $OPENACS_SERVICE_NAME
  [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ createdb -E UNICODE $OPENACS_SERVICE_NAME
  CREATE DATABASE

• Automate daily database Vacuuming. This is a process which cleans out discarded data from the database. A quick way to automate vacuuming is to edit the cron file for the database user. Recommended: VACUUM ANALYZE every hour and VACUUM FULL ANALYZE every day.

  [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ export EDITOR=emacs;crontab -e

  Add these lines to the file. The vacuum command cleans up temporary structures within a PostGreSQL database, and can improve performance. We vacuum gently every hour and completely every day. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day, and every (*) day of month, month, and day of week. Type man 5 crontab for more information.

  0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --analyze $OPENACS_SERVICE_NAME
  0 0 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze $OPENACS_SERVICE_NAME

  Depending on your distribution, you may receive email when the crontab items are executed. If you don't want to receive email for those crontab items, you can add > /dev/null 2>&1 to the end of each crontab line

  At this point the database should be ready for installing OpenACS.

Configure an AOLserver Service for OpenACS.

1. The AOLserver architecture lets you run an arbitrary number of virtual servers. A virtual server is an HTTP service running on a specific port, e.g. port 80. In order for OpenACS to work, you need to configure a virtual server. The Reference Platform uses a configuration file included in the OpenACS tarball, /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/config.tcl. Open it in an editor to adjust the parameters.

   [root root]# su - $OPENACS_SERVICE_NAME
   [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc
   [$OPENACS_SERVICE_NAME etc]$ emacs config.tcl
   

   You can continue without changing any values in the file. However, if you don't change address to match the computer's ip address, you won't be able to browse to your server from other machines. See en:aolserver-admin for an explanation of some other values you might want to change in the config.tcl file.

Verify AOLserver startup.

1. Kill any current running AOLserver processes and start a new one. The recommended way to start an AOLserver process is by running the included script, /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/daemontools/run. If you are not using the default file paths and names, you will need to edit run.

   If you want to use port 80, there are complications. AOLserver must be root to use system ports such as 80, but refuses to run as root for security reasons. So, we call the run script as root and specify a non-root user ID and Group ID which AOLserver will switch to after claiming the port. To do so, find the UID and GID of the $OPENACS_SERVICE_NAME user via grep $OPENACS_SERVICE_NAME /etc/passwd and then put those numbers into the command line via -u 501 -g 502. In AOLserver 4, you must also send a -b flag. Do this by editing the run file as indicated in the comments.

   If you are root then killall will affect all OpenACS services on the machine, so if there's more than one you'll have to do ps -auxw | grep nsd and selectively kill by job number.

   [$OPENACS_SERVICE_NAME etc]$ killall nsd
   nsd: no process killed
   [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ /usr/local/aolserver/bin/nsd-postgres -t /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/config.tcl
   [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ [08/Mar/2003:18:13:29][32131.8192][-main-] Notice: nsd.tcl: starting to read config file...
   [08/Mar/2003:18:13:29][32131.8192][-main-] Notice: nsd.tcl: finished reading config file.

2. Attempt to connect to the service from a web browser. You should specify a URL like: http://yourserver.test:8000

   You should see a page that looks like this, otherwise check the en:aolserver-admin Troobleshooting secton.

Configure a Service with the OpenACS Installer. Now that you've got AOLserver up and running, let's install OpenACS 5.2.0d1.

• You should see a page from the webserver titled OpenACS Installation: Welcome. You will be warned if your version of the database driver is out of date, if AOLserver cannot connect to the database, if any modules are missing or out-of-date, or if there are any problems with filesystem permissions on the server side. But if everything is fine, you can click Next to proceed to load the OpenACS Kernel data model.

• The next page shows the results of loading the OpenACS Kernel data model - be prepared to wait a few minutes as it works. You should see a string of output messages from the database as the datamodel is created. You'll see the line:

  Loading package .info files ... this will take a few minutes

  This will really take a few minutes. Have faith! Finally, another Next button will appear at the bottom - click it.

• The following page shows the results of loading the core package data models. You should see positive results for each of the previously selected packages, but watch out for any errors. Eventually, the page will display "Generating secret tokens" and then "Done"- click Next.

• You should see a page, "OpenACS Installation: Create Administrator" with form fields to define the OpenACS site administrator. Fill out the fields as appropriate, and click Create User.

• You should see a page, "OpenACS Installation: Set System Information" allowing you to name your service. Fill out the fields as appropriate, and click Set System Information

• You'll see the final Installer page, "OpenACS Installation: Complete." It will tell you that the server is being restarted; note that unless you already set up a way for AOLserver to restart itself (ie. inittab or daemontools), you'll need to manually restart your service.

  [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ /usr/local/aolserver/bin/nsd-postgres -t /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/config.tcl

• Give the server a few minutes to start up. Then reload the final page above. You should see the front page, with an area to login near the upper right. Congratulations, OpenACS <version> is now up and running!

ref: https://openacs.org/doc/openacs.html

Books and publications about OpenACS

Created by Benjamin Brink, last modified by Gustaf Neumann 08 Aug 2017, at 09:39 AM

Listed in chronological order, newest first.

Aram, Koch, Neumann. "Long-Term Analysis of the Development of the Open ACS Community Framework: Open Source Solutions for Knowledge Management and Technological Ecosystems" c2017 http://www.igi-global.com/chapter/long-term-analysis-of-the-development-of-the-open-acs-community-framework/168981

Demetriou, Koch, Neumann. "The Development of the OpenACS Community" http://nm.wu-wien.ac.at/research/publications/b608.pdf  A chapter from: Miltiadis Lytra, Ambjorn Naeve (eds): Open Source for Knowledge and Learning Management: Strategies Beyond Tools, Idea Group Publishing, Hershey, PA, 2006.

Andersson, Greenspun, Grumet. "Software Engineering for Internet Applications" c2006 http://philip.greenspun.com/seia/ "A 2002 textbook for MIT students learning how to build things like amazon.com"

Abelson, Greenspun, Sandon. "Tcl for Web Nerds" http://philip.greenspun.com/tcl/ "We hope that a professional programmer or MIT student can breeze through it in one evening. By the end of the evening, that person should have learned Tcl, learned a little something about the Web, and not have been bored."

Philip Greenspun. "SQL for Web Nerds" http://philip.greenspun.com/sql/: ..we keep our readers in the world of Web services. Most often they are working within the data model for online communities.. ..our examples are all drawn from real production Web sites that get close to 1 million requests per day. This should make the examples more interesting.. ..we assume that our readers are bright and accustomed to formal languages. We don't assume any experience with declarative languages, database query languages, or any specific programming language. But once we can assume that the reader has written code, it is possible to use more sophisticated examples and get to the interesting stuff more quickly. ..we hope that ..[its].. a great choice for the MIT student or the working programmer.

Philip Greenspun. "Philip and Alex's Guide to Web Publishing"; c1998 http://philip.greenspun.com/panda/ A historical classic that introduced some early developers to the components and thinking behind OpenACS

2006 International Workshop on Community Based E-Learning Systems

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 27 Jul 2017, at 10:10 AM

Keynotes and Schedule 

One day conferences on E-learning and online communities. This conference is a evolution of previous conferences on e-learning technologies and related topics held since 2003 in several locations (Denmark, Germany, Spain) by former and actual .LRN (dot-learn) consortium members. This is day one in the two day Fall Conference 2006 (you will find details on that page).

Questions? Write us.

When: 1st. of November 2006.

Call for abstracts (25-250 words) for workshops, talks, or sessions: deadline 30th of September 2006. Please email your abstract.

Add yourself to the Fall_Conference_2006_Interest_in_Attending list (this is a non-binding list to help people connect at the conference and after the conference).

Possible Topic Areas:

• Automated Testing
• Methodologies for online teaching
• Content development approaches
• Educational standards support
• Usability for online learning
• Accessible services for learners
• Experiences and Best Practices
• Helping users do what they want to do (creating happy users)

Program Committee:

• Carl Blesius, MGH Lab of Computer Science, U.S.A.
• Alfred Essa, U.S.A.
• Gustaf Neumann, University of Viena, Austria.
• Carlos Delgado Kloos, UC3M, Spain.
• Jesús G. Boticario, UNED, Spain.
• Emmanuelle Raffenne, UNED, Spain.
• Olga C. Santos, aDeNu Research Group, UNED, Spain.
• Rocael Hernández, Galileo University, Guatemala. 

Organization Committee:

• Carl Blesius, MGH Lab of Computer Science, U.S.A.
• Emmanuelle Raffenne, UNED, Spain
• Rocael Hernández, Galileo University, Guatemala
• Katherine Lau, MGH Lab of Computer Science, U.S.A.
• Olga C. Santos, aDeNu Research Group, UNED, Spain

Morning Talks (in the Rotunda Auditorium)

The morning session will be in front of the entire group. We hope to have an amazing keynote speaker at the start of morning (to be announced) and then pick the best submissions from the abstracts which are still coming in.

List of afternoon sessions (in the breakout rooms)

• Towards full Accessibility in LMS
• User interface guidelines
• Informal workshops (i18n, CSS/Semantic Markup, ___)

 The Submission list is being built here:

Fall_Conference_2006_Submissions

for everyone

Created by OpenACS community, last modified by Benjamin Brink 22 Jul 2017, at 11:49 PM

OpenACS for everyone

OpenACS (Open Architecture Community System) is:

• an advanced toolkit for building scalable, community-oriented web applications.
• a robust, scalable framework (see: en:openacs-system) for building dynamic content driven sites and enterprise-level web applications.
• a collection of pre-built applications and services that you can build on to create a custom web-site or application.
• derived from the ArsDigita Community System (ACS). ArsDigita (now part of Red Hat, Inc.) kindly made their work available under the GPL, making all of this possible.

Through a modular architecture, OpenACS has packages for user/groups management, content management, e-commerce, news, FAQs, calendar, forums, bug tracking, wiki (XoWiki), full-text searching etc. See OpenACS repository.

Strengths

• Ready "out of the box" for common features of collaborative web sites. See en:feature-summary
• Proven Architecture. Components of the OpenACS (see en:openacs-system) are proving themselves in the most demanding of applications
• Designed for scalability See: http://en.wikipedia.org/wiki/Scalability#Design_for_scalability
• Proven in the field. OpenACS is working well, deployed at sites that have upwards of 40K users (See e.g. AIESEC at OpenACS sites)
• Responsive Community See: en:community-culture
• Commercial Support In addition to Commercial Support, there are many independent consultants available for hire. This collection of commercial providers work together to maintain OpenACS in addition to competing for clients. Sometimes vendors work together for the same client. Most importantly, no client is ever left without support, even if his or her original provider goes out of business.
• Documentation is continually evolving and improving. (See: en:Documentation_Project)
• Institutional commitment. Including MIT Sloan School of Management which has initiated and led the development of .LRN, an open-source courseware system built on OpenACS. (See Institutions supporting .LRN)
• Extensible See: http://en.wikipedia.org/wiki/Extensible

Use the OpenACS fourms to contact the OpenACS community. We welcome your feedback and can help with your OpenACS endeavors. Commercial support is also available.

What others say about OpenACS

• ohloh.net valuates Open Source projects, and OpenACS' is here: http://www.ohloh.net/projects/3877 and http://www.ohloh.net/projects/3877/analyses/latest along with an OpenACS thread elaborating on it.
• One users review of OpenACS, comparing it to LAMP, .NET, and the competition.
• What I saw at the revolution: .LRN/OpenACS meetings in Heidelberg, Germany, http://www.octavianworld.org/octavianworld/2004/04/what_i_saw_at_t.html#more, 2004 by Cesar Brea
• FLOSS Usability sprint
• Why a reluctant coder chooses OpenACS for building killer apps
• Why a reluctant coder chooses OpenACS smorgasbord app framework over meal-in-a-box apps
• Why a reluctant coder chooses OpenACS in spite of imperfect documentation
• Why a reluctant coder chooses OpenACS though its missing generic features
• Why a reluctant coder chooses OpenACS when learning other ways seems so easy
• Why a reluctant coder chooses OpenACS app framework library
• Why a reluctant coder chooses OpenACS when other frameworks measure much faster
• Why a reluctant coder chooses “trashy looking” and “hard to use” OpenACS

Others' descriptions of OpenACS

• http://www.cmsmatrix.org/matrix/cms-matrix/openacs
• https://en.wikipedia.org/wiki/OpenACS
• http://www.cmsreview.com/timelines/ShopComparison.html?SelectedList=Product20;

Testimonials posted to forums on OpenACS

• OpenACS #1 for high traffic websites (Aug 2013 sample)
• One week after switching to naviserver from aolserver on openacs.org (Aug 2013)
• How does OpenACS Scale?

Try OpenACS

History of OpenACS

See: History of OpenACS en:docs-history

Bibliography and Credits

See: Documentation Credits en:doc-credits

Quota

Created by Gustaf Neumann, last modified by Benjamin Brink 07 Jul 2017, at 07:34 AM

Package Specification Summary for Package: quota

Bug Tracker Summary for Package: quota

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

Code Metrics Summary for Package: quota

Quota 

Package to control the expense of space in users' disc and communities.

The module quota allows to control the space used by users and communities in the module filestorage, this is controlled by the manager of the system and for it it he can modify the global parameters and to establish particular values of these parameters for communities and even users.

The available parameters are:

MaxQuotaByCommunity - > maximum Quota for community (in KB)

MaxQuotaByUser - > maximum Quota for user (in KB)

MaxQuotaByUserFolder - > maximum Quota of the personal directoryof the user (in KB)

MaxQuotaByUserComm - > maximum Quota for user in a community (in KB)

MaxFilesByCommunity - > N º maximum of files for community

MaxFilesByUser - > N º maximum of files for user

MaxFilesByUserFolder - > N º maximum of files for personal directory

MaxFilesByUserComm - > N º maximum of files for user in a community

QUOTA

Created by Francisco Soler Lahuerta, last modified by Benjamin Brink 07 Jul 2017, at 07:33 AM

see en:quota

Wikipedia

Created by Gustaf Neumann, last modified by Benjamin Brink 07 Jul 2017, at 07:32 AM

Package Specification Summary for Package: wikipedia

Bug Tracker Summary for Package: wikipedia

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

Code Metrics Summary for Package: wikipedia

Integration of the encyclopedia Wikipedia in dotLRN. 

Accomplishment of a module integrated to the platform dotLRN, that allows to realize searches in the encyclopedia wikipedia, without need to go out of the platform.

The consultations turn out to be integrated to the course or community and can be realized in different languages.

Wikipedia

Created by Agustín Lopez Bueno, last modified by Benjamin Brink 07 Jul 2017, at 07:32 AM

see en:wikipedia

for administrators

Created by OpenACS community, last modified by Benjamin Brink 07 Jul 2017, at 07:15 AM

Getting admin-level help

Install OpenACS

Setup database environment variables. See end of https://openacs.org/doc/openacs.html,

https://openacs.org/doc/backup-recovery.html, and https://openacs.org/doc/snapshot-backup.html

https://openacs.org/doc/analog-setup.html

For creating custom pages, see developer tutorials https://openacs.org/doc/tutorial.html

Administrating a system

• en:aolserver-admin
• en:postgresql-admin
• en:oracle-notes
• en:openacs_monitoring
• en:system-security

These OpenACS packages are useful for diagnostics and development:

• en:acs-developer-support
• en:acs-api-browser
• en:schema-browser 
• NaviServer nsstats
• server log at {openacs-root-directory}/log/error.log

Performance monitoring

• en:openacs_monitoring
• en:openacs-performance-tuning
• NaviServer nsstats

Bibliography and Credits

See en:doc-credits.

Administrators - Req.

Created by OpenACS community, last modified by Benjamin Brink 07 Jul 2017, at 07:11 AM

Site and System Administrators - Documentation Requirements

By the OpenACS Community. This section is a collection of documentation requirements that have been expressed in the OpenACS forums to 4th July 2003.

OpenACS administrators' documentation should meet the following requirements. No significance has been given to the order presented, topic breadth or depth here.

• For each requirement below, include links to developer tutorials and other documentation for more detail.

• Describe a structural overview of a working system and how the components work together. "The Layered Cake view" a general network view of system; a table showing system levels versus roles to help with understanding how the subsystems are interconnected.

• Provide a comprehensive description of typical administrative processes for operating an OpenACS system responsibly, including reading logs and command line views that describe status of various active processes.

• Create a list of administrative tools that are useful to administrating OpenACS, including developer support, schema-browser and api browser. Link to AOLserver's config file documentation.

• Resources on high level subjects such as web services, security guidelines

• Describe typical skill sets (and perhaps mapped to standardized job titles) for administrating an OpenACS system (human-resources style). For a subsite admin/moderator attributes might include trustworthy, sociable, familiarity with the applications and subsystems, work/group communication skills et cetera

• Describe how to set up typical site moderation and administration including parameters, permissions, "Hello World" page

• Show directory structure of a typical package, explanation of the various file types in a package (tcl,adp,xql) and how those relate to the previously described subsystems, when they get refreshed etc.

• Ways to build a "Hello World" page

• Show examples of how the OpenACS templating system is used, including portal sections of pages. For example, create a customised auto-refreshing startpage using lars-blogger, a photo gallery, and latest posts from a forum. This should rely heavily on documentation existing elsewhere to keep current. This would essentially be a heavily annotated list of links.

• Show ways of modifying the look and feel across pages of an OpenACS website. Refer to the skins package tutorial.

• Describe a methodology for diagnosing problems, finding error statements and interpreting them --for OpenACS and the underlying processes.

• FAQs: Administration tasks commonly discussed on boards: admin page flow, how to change the looks of a subsite with a new master.adp, options on "user pages" , a quick introduction to the functions and processes. info about the user variables, file locations

Pull in docs from: https://openacs.org/doc/acs-admin.html