Here is how an OpenACS 5 server is laid out starting from the Server root (ROOT):
Figure 11.1. Server file layout
+ Figure 11.1. Server file layout
diagram Figure 11.2. Package file layout
+ Figure 11.2. Package file layout
diagram Table 11.1. Package
+ Table 11.1. Package
files The following sections will show you how to make a package for
the Notes application. In addition, they will discuss some site
management features in OpenACS 5 that take advantage of the
-APM's package instance model. The two most important of these
+APM's package instance model. The two most important of these
are subsites, and the
site map tool, which can be
used to map applications to one or more arbitrary URLs in a running
@@ -325,7 +325,7 @@
(install, instantiate, mount)" link. The new package has been created and installed in the server. At
this point, you should add your package files to your CVS
-repository. I'll assume that you have set up your development
+repository. I'll assume that you have set up your development
repository according to the standards described in this appendix. If so, then
you just do this:
ROOT/
bin/
@@ -65,7 +65,7 @@
To illustrate
the general structure of a package, let's see what the package
for the "notes" application should look like.
ROOT/
+-- packages/ APM Root
@@ -136,7 +136,7 @@
files are not sourced in these directories. This makes it suitable
for storing icons, css files, javascript, and other static content
which can be treated this way.
% cd ROOT/packages
@@ -401,8 +401,8 @@
Additional Reading