zeek/doc
Robin Sommer e0c4bd1a82 Lots of cleanup and API documentation for the analyzer/* classes.
I've used the opportunity to also cleanup DPD's expect_connection()
infrastructure, and renamed that bif to schedule_analyzer(), which
seems more appropiate. One can now also schedule more than one
analyzer per connection.

TODOs:
        - "make install" is probably broken.
        - Broxygen is probably broken for plugin-defined events.
        - event groups are broken (do we want to keep them?)
        - parallel btest is broken, but I'm not sure why ...
          (tests all pass individually, but lots of error when running
          in parallel; must be related to *.bif restructuring).
        - Document API for src/plugin/*
        - Document API for src/analyzer/Analyzer.h
        - Document API for scripts/base/frameworks/analyzer
2013-04-01 13:12:21 -07:00
..
_static Tweaks. 2012-01-09 18:28:43 -08:00
_templates s/bro-ids.org/bro.org/g 2013-03-07 19:33:04 -08:00
bin Changes to Broxygen master script package index 2011-12-02 13:59:33 -06:00
components Submodule README conformity changes 2011-11-29 12:18:42 -06:00
ext Remove deprecated attribute &disable_print_hook 2012-09-26 16:47:51 -05:00
images Adapt more www niceties to broxygen (stylesheets, pygments); add more docs 2011-11-15 15:39:31 -06:00
scripts Lots of cleanup and API documentation for the analyzer/* classes. 2013-04-01 13:12:21 -07:00
.gitignore A set of script-reference polishing. 2012-01-09 18:04:34 -08:00
CHANGES Fix documentation interlinkage and normalize console directive bodies. 2011-11-15 16:27:06 -06:00
cluster.rst Fix minor typos in documentation 2012-02-02 18:48:23 -06:00
CMakeLists.txt Add missing doc targets to top Makefile; remove old doc/Makefile. (fixes #705) 2011-12-01 09:16:38 -06:00
conf.py.in A set of script-reference polishing. 2012-01-09 18:04:34 -08:00
faq.rst Move upgrade instructions to INSTALL document 2012-10-23 13:51:43 -05:00
geoip.rst Adapt more www niceties to broxygen (stylesheets, pygments); add more docs 2011-11-15 15:39:31 -06:00
index.rst s/bro-ids.org/bro.org/g 2013-03-07 19:33:04 -08:00
input.rst rename the update_finished event to end_of_data and make it fire in 2012-10-10 11:51:20 -07:00
INSTALL.rst Adapt more www niceties to broxygen (stylesheets, pygments); add more docs 2011-11-15 15:39:31 -06:00
intel.rst Merge remote-tracking branch 'origin/topic/seth/intel-framework' 2012-11-01 08:21:52 -07:00
logging-dataseries.rst Fix minor typos in dataseries documentation 2012-07-03 18:20:52 -05:00
logging-elasticsearch.rst More documentation updates. 2012-07-20 11:02:09 -04:00
logging.rst Linking ES docs into logging document. 2012-08-21 08:42:09 -07:00
notice.rst Merge remote-tracking branch 'origin/topic/seth/notice-framework-updates' 2013-03-06 16:45:30 -08:00
quickstart.rst s/bro-ids.org/bro.org/g 2013-03-07 19:33:04 -08:00
README corrected some minor typos 2012-01-11 13:02:12 -06:00
reporting-problems.rst s/bro-ids.org/bro.org/g 2013-03-07 19:33:04 -08:00
signatures.rst Add IPv6 support to signature header conditions. 2012-10-17 11:11:51 -05:00
upgrade.rst s/bro-ids.org/bro.org/g 2013-03-07 19:33:04 -08:00

Documentation
=============

This directory contains Bro documentation in reStructuredText format
(see http://docutils.sourceforge.net/rst.html).

It is the root of a Sphinx source tree and can be modified to add more
common/general documentation, style sheets, JavaScript, etc.  The Sphinx
config file is produced from ``conf.py.in``, and can be edited to change
various Sphinx options.

There is also a custom Sphinx domain implemented in ``source/ext/bro.py``
which adds some reST directives and roles that aid in generating useful
index entries and cross-references.  Other extensions can be added in
a similar fashion.

Either the ``make doc`` or ``make broxygen`` targets in the top-level
Makefile can be used to locally render the reST files into HTML.
Those targets depend on:

* Python interpreter >= 2.5
* `Sphinx <http://sphinx.pocoo.org/>`_ >= 1.0.1

After completion, HTML documentation is symlinked in ``build/html``.

There's also ``make docclean`` and ``make broxygenclean`` targets to
clean the resulting documentation.

Notes for Writing Documentation
-------------------------------

* If you want to refer to a document that's part of the
  distribution, it currently needs to be copied or otherwise symlinked
  somewhere in to this Sphinx source tree. Then, it can be referenced
  in a toc tree or with the :doc: role.  Use the :download: role to
  refer to static files that will not undergo sphinx rendering.

* If you want to refer to a page on the Bro web site, use an HTTP URL.

Guidelines
----------

TODO.