On 02-02-18 15:04:13 CET, Michael Bell wrote:
> Hi,
>
> I think we should continue the discussion in a more public way.
>
> The actual installation knows four "big" places:
>
> * cgi-bin
> * htdocs
> * OpenCA/ca
> * OpenCA/ext
>
> I want to establish a structure like this
>
> * cgi-bin (with only one directory and script per server)
> * htdocs (like today)
> * OpenCA/ca (like today)
> * OpenCA/ext (like today)
> * OpenCA/src (perlcode which must not be placed in cgi-bin)
> # conf/ (perhaps the wrong place - OpenCA/ca/conf/ or
> OpenCA/src/ca/conf is better)
> # cmds/
> # lib/
> # ca/
> + sheets/
> + messages/
> + cmds/ (links to the commands)
> # ra/
> + sheets/
> + cmds/
> # pub/
> + sheets/
> + messages/
> + cmds/
>
> I need the many new options to configure and test this structure. So
> Robert, what do you think about this structure? You have normally the
> better ideas for the installation :)
typically, one has three classes of files.
- read-only files in /usr/{bin,lib}, written only at the time of installation
- files to be adjusted by some administrator in /etc
- writeable files in /var
what have we got?
- the htdocs and cgi-bin files are somewhat exempt, because they will
usually follow the httpd file hierarchy layout (unless somebody wants to
fiddle their httpd.conf file).
- perl code in two varieties, lib-style (used by other code, like one
finds in /usr/lib/perl5) and command-style (fulfilling one purpose,
like in /usr/bin if called directly or /usr/lib if called indirectly
through a program).
- templates for html output: lib-style
- dbm files: var-style
i guess i have to reread last fall's discussion for a more detailed
proposal...
> I think ca/, ext/ and src/ on the same level (OpenCA/) looks not really
> nice.
i agree, it mixes two quite different things.
rj
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel
