| Prev | Chapter�10.�Development Reference | Next |
|---|
By Pete Su and Bryan Quinn
+Here is how an OpenACS 5 server is laid out starting from the Server root (ROOT): -
Figure�10.1.�Server file layout diagram
+Figure�11.1.�Server file layout diagram
ROOT/ bin/ Various executables and scripts for server maintanence. @@ -51,7 +51,7 @@ To illustrate the general structure of a package, let's see what the package for the "notes" application should look like. -Figure�10.2.�Package file layout diagram
+Figure�11.2.�Package file layout diagram
ROOT/ +-- packages/ APM Root | @@ -124,7 +124,7 @@ directories. This makes it suitable for storing icons, css files, javascript, and other static content which can be treated this way. -Table�10.1.�Package files
File Type Its Use Naming Convention Package Specification File The package specification file is an XML file generated and + Table�11.1.�Package files
File Type Its Use Naming Convention Package Specification File The package specification file is an XML file generated and maintained by the OpenACS Package Manager (APM). It specifies information about the package including its parameters and its files. notes.info Data Model Creation Script @@ -333,7 +333,7 @@ this point, you should add your package files to your CVS 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: + this appendix. If so, then you just do this: % cd ROOT/packages % cvs add notes % cd notes @@ -411,4 +411,4 @@Writes out package distribution files for other people to download and install. We'll cover this later. -
($Id$)View comments on this page at openacs.org +($Id$)View comments on this page at openacs.org