|
|
|
Version 0.4.2
|
|
|
|
-----------
|
|
|
|
# Version 1.0
|
|
|
|
|
|
|
|
Welcome to the Developer’s guide.
|
|
|
|
|
|
|
|
This document will guide you through the stages of Module and Report
|
|
|
|
development and teach you how to develop your own Modules and Reports in
|
|
|
|
just a few minutes.
|
|
|
|
This document will guide you through the stages of component development and teach
|
|
|
|
you how to develop your own components in just a few minutes.
|
|
|
|
|
|
|
|
## [Coding guidelines](http://rubydoc.info/github/Arachni/arachni/file/HACKING.md)
|
|
|
|
|
|
|
|
[Coding guidelines](http://rubydoc.info/github/Arachni/arachni/file/HACKING.md)
|
|
|
|
------------------------------------------------------------------------
|
|
|
|
|
|
|
|
This should be your first stop for module development, it will give you
|
|
|
|
the skinny on hacking around with the framework.
|
|
|
|
If that’s not enough to get you started there’s no need to worry, the
|
|
|
|
next chapters will explain the process in detail.
|
|
|
|
|
|
|
|
Component development
|
|
|
|
---------------------
|
|
|
|
## Component development
|
|
|
|
|
|
|
|
Every modular aspect of Arachni is abstracted in the form of
|
|
|
|
*components* .
|
| ... | ... | @@ -87,13 +84,11 @@ Dispatcher and whose API can be exposed via the regular RPC interface. |
|
|
|
These components provide a way to extend the server-side functionality with
|
|
|
|
extra features.
|
|
|
|
|
|
|
|
[Core API](http://rubydoc.info/github/Arachni/arachni)
|
|
|
|
---------------------------------------------------------
|
|
|
|
## [Core API](http://rubydoc.info/github/Arachni/arachni)
|
|
|
|
|
|
|
|
Automatically generated documentation of the Arachni code-base.
|
|
|
|
|
|
|
|
[[RPC API | RPC API]]
|
|
|
|
---------------------
|
|
|
|
## [[RPC API | RPC API]]
|
|
|
|
|
|
|
|
Detailed documentation on using the RPC API to interact with the Arachni
|
|
|
|
servers (Dispatcher/Instance) or write your own client. |
