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)
i get a headache looking at it. it mixes so many different things? .../ca .../ca/stuff .../ca/chain .../ca/private .../ca/dB .../ca/p12 .../ca/tmp .../ca/inbound .../ca/inbound/reqs .../ca/inbound/misc .../ca/outbound .../ca/outbound/crl .../ca/outbound/certs .../ca/outbound/mail .../ca/outbound/misc .../ca/outbound/ca .../ca/conf .../ca/conf/misc .../ca/conf/openssl .../ca/conf/openssl/extfiles .../ca/conf/openssl/openssl .../ca/conf/rbac .../ca/conf/rbac/modules .../ca/conf/rbac/operations .../ca/conf/rbac/rights .../ca/conf/rbac/roles .../ca/conf/rbac/scripts the openssl config is the same everywhere? (actually being used on the CA, just for reference elsewhere?) what is "stuff"? why is there a separate chain directory? what is p12 for? what parts of the structure are due to how openssl works (what files it expects to find), what parts are our own additions? i get confused everytime i look at it. is anybody able to explain it to me? i would like to restructure it so that people like me, who don't work on openca every week, can understand it at a glance. > * 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) what for? why not use them from one level up directly? rj _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
