Forum OpenACS Development: Make openacs4.tcl the live AOLserver config file
Presumably, we would still like the config file to be viewable as part of the online docs, yes? (The section showing the real database password should be first broken out into a small separate file not viewable from the online docs.) Other than symlinks, what ways are there to do this?
What do you think?
/nsd/and why would we want to put it there?
Using "etc" as the directory name also sounds ok. It's less specific, but that's probably fine, arguably even better.
/web/(servername); the config, ssl, daemontools, and all the stuff like that go in
/web/servername/etcor subdirectories thereof.
The guy doing the gentoo port got rid of "nsadmin" and I agree that we should stop using the "ns" language wherever it's easy to do so, because it's confusing to newcomers.
What I'd definitely still like to hear about is people's take on moving the existing OpenACS AOLserver config file out of the docs where it's buried, and putting it where we're suggesting folks keep their operational AOLserver config file. Plus the related "should we jump through some hoops, and what hoops, to make the AOLserver config file browseable online" question.
CVS acts slightly suprisingly with respect to empty directories, so
you might want to add directories only if we have files to put in
them. But, that's just a minor taste thing, either way there's really
no harm. Important thing is if we do have good
etc/nsd.tcl or whatever other config files to distribute
with OpenACS, then yeah, let's definitely create the directories and
put them there.
I think yes we should create the additional dirs, we should definitely create etc and put the config file. These things will make the install steps more simple. Even just a little. Also regarding the blank dirs. I would suggest to put a README file on it. Even one liner. Like "This dir is used to put the service files of daemontools. If you are not using deamontools you can safely delete this dir".
If anyone has a good shell script maybe we can put a simple shell script to start the aolserver instance. It would be better if its easier and easier for a newbie to try OpenACS. The tweaking and performance stuff will come when someone is already familiar with OpenACS. To lower the barrier is always good.
I am trying to catch up with OACS. I recently glaced at your docs, its good. I did however put a small twist on my install. I put the OACS files in ~/web of the user that will run that instance. Normally my old config in II was each user run once instance of OACS. So I still adopted something similar but basically your layout. But the files are in the users home dir. I think its not LSB, oh well.
Andrew: I think the config file that should be viewable should be the sample one, not the real one. We can leave placeholders in the CVS (something like "YOUR_DB_USER_HERE" or the like).