Re: [naviserver-devel] hey hey wiki

[Stephen D. <sd...@gm...>]

On 6/29/05, Bernd Eidenschink <eid...@we...> wrote:
>=20
> Hi NaviCoders,
>=20
> I played a bit with the Wiki and started to add something to a Documentat=
ion
> section. Would be cool if you could just take a quick look the next days =
(no
> hurry) and rearrange/debug what you think fits better or is more logical.


Looks good.  Thanks!

I was thinking the wiki might be best suited to task-specific
documentation?  For example, rather than list all commands and give an
example of each, we might have a page 'Returning Data' which shows how
to use ns_return, ns_returnfile, ..., how to write headers and stream
content with ns_write, how to choose between them, etc.  Then we might
have a page called 'Performance Tuning' which would describe which
config file settings affect performance, settings for your OS, how to
use the stats interface for gathering data, etc.

The formal API documentation in CVS will be the first place to go when
you have a specific question about how the server works.  When you
have a goal in mind -- tune the server, write a form that accepts file
uploads, set up virtual hosts -- you'll read an article on the wiki.

Makes sense?


> Stephen, do you know how to make backups from that MySQL-stuff the easy w=
ay?


You have to login to the SF shell server using ssh and dump the db.=20
SF don't like you to leave the dump lying around on the server, so
maybe a couple of cron jobs that dump and then cleanup an hour later,
allowing project admins to scp the contents would do the trick?

Need to figure this out and create an 'Admin' page on the wiki...