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
Updated Development environment (markdown) authored Mar 26, 2013 by Zapotek's avatar Zapotek
Hide whitespace changes
Inline Side-by-side
guides/developer/Development-environment.md
View page @ bf227b3f
...@@ -19,6 +19,8 @@ The following will build and setup a self-contained environment for you: ...@@ -19,6 +19,8 @@ The following will build and setup a self-contained environment for you:
The ```ARACHNI_BUILD_ENV=development``` env tells the build-scripts to preserve 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 development headers of all the libraries it installs so that you'll be able to
install more gems inside that env if need be. install more gems inside that env if need be.
(If you don't plan on installing extra gems you can leave the ```ARACHNI_BUILD_ENV```
variable undefined and save some space.)
Finally, if you are using RVM, put this in your ```.rvmrc``` file: Finally, if you are using RVM, put this in your ```.rvmrc``` file:
...@@ -32,3 +34,5 @@ Finally, if you are using RVM, put this in your ```.rvmrc``` file: ...@@ -32,3 +34,5 @@ Finally, if you are using RVM, put this in your ```.rvmrc``` file:
If not using RVM you'll have to run the above manually when working from the If not using RVM you'll have to run the above manually when working from the
terminal while developing Arachni. terminal while developing Arachni.
(I suggest putting the above in a shellscript named ```arachni-setenv.sh```
and running it from the same terminal you plan to use to test/run/dev with 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
    • Development environment
  • 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?