Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Wiki
  • Guides
  • Developer
  • Development environment

Development environment · Changes

Page history
added guide to setting up a dev env authored Mar 06, 2013 by Tasos Laskos's avatar Tasos Laskos
Show whitespace changes
Inline Side-by-side
guides/developer/Development-environment.md 0 → 100644
View page @ ef939692
# Setting up a development environment
In order to ensure that what you'll be experiencing during development will be
what the end-user will experience in terms of stability, performance and
compatibility, the preferred way to setup a development environment is
to essentially work from inside one of Arachni's self-contained packages.
Actually, this makes setting up a development environment even easier as
you won't have to go digging through dependencies or affecting the libraries
and packages of your workstation at all.
All this goodness is facilitated by the project's [build scripts](https://github.com/Arachni/build-scripts).
The following will build and setup a self-contained environment for you:
ARACHNI_BUILD_ENV=development wget -O - https://raw.github.com/Arachni/build-scripts/master/bootstrap.sh | bash
The ```ARACHNI_BUILD_ENV=development``` env tells the build-scripts to preserve
development headers of all the libraries it installs so that you'll be able to
install more gems inside that env if need be.
Finally, if you are using RVM, put this in your ```.rvmrc``` file:
# Clear RVM's env overrides to make room for ours
rvm reset
# Get us into the package env
export env_root=/home/<username>/arachni-build-dir/arachni/system
source $env_root/environment
export PATH=$env_root/gems/bin:$PATH
If not using RVM you'll have to run the above manually when working with the
terminal while developing Arachni.
Clone repository

Pages [all]


  • Home
  • Installation instructions
  • For users
    • Executables
    • Command Line Interface
    • Web User Interface
    • RPC Client
    • RPC Server (Dispatcher)
  • For developers
    • Coding guidelines
    • Core API documentation
    • RPC API
  • Technology
    • The Brains
    • Distributed components (Dispatchers and Instances)
    • High Performance Grid

Can't find what you're looking for? Why not have a look at the support portal?