Frequently Asked Questions¶
- I need special command to get my code
- Can I checkout that branch?
- Can I clone with my ssh keys?
- The project is too big
- How can I run a very large project?
- Where can I find the report
- Can I run exakat on local code?
- Can I ignore a dir or a file?
- Can I run Exakat with PHP 5?
- I get the error ‘The executable ‘ansible-playbook’ Vagrant is trying to run was not found’
- Can I run exakat on Windows?
- Does exakat send my code to a central server?
If Exakat has no documented method to reach your code, you may use this process :
php exakat.phar init -p <your project name> cd ./projects/<your project name> mkdir code // here, do whatever it takes to put all your code in 'code' folder cd - php exakat.phar project -p <your project name>
Send a message on Github.com/exakat/exakat to mention your specific method.
Currently (Version 0.12.2), there is no way to request a tag or a branche or a revision when cloning the code.
The best way is to reach the ‘code’ folder, and make the change there. Unless with ‘init’ or ‘update’, exakat doesn’t make any change to the code.
php exakat.phar init -p myProject -R url://my/git/repository cd ./projects/myProject/code git branch notMasterBranch cd - php exakat.phar project -p myProject
When using git, or any vcs, the current shell user’s SSH keys may be used to access the repository. When using a remote installation, or a docker image, the keys won’t be accessible.
The fallback solution is to init an empty project, clone the code from the Shell (with the keys), and then run project.
php exakat.phar init -p myProject cd ./projects/myProject git clone url://myprivate/git/repository code cd - php exakat.phar project -p myProject
There is a soft limit in config/exakat.ini, called ‘token_limit’ that initially prevents analysis of projects over 1 millions tokens. That’s roughly 125k LOC, more than most code source.
If you need to run exakat on larger sources, you may change this value to make it as large as possible. Then, the physical capacities of the machine, specially RAM, will be the actual limit.
It may be interesting to ‘ignore_dir’, from projects/<>/config.ini.
Here are a few steps you can try when running exakat on a very large project.
- Update project/<name>/config.ini, and use ignore_dirs and include_dirs to exclude as much code as possible. Notably, frameworks, data in PHP files, tests, cache, translations, etc.
- Set $JAVA_OPTIONS to large quantities of RAM : JAVA_OPTIONS=’-Xms1024m -Xmx6096m’;
- Check that your installation is running with ‘gsneo4j’ and not ‘tinkergraph’, in config/exakat.ini.
Reports are available after running at least the following commands :
php exakat.phar init -p <your project name> -R <code source repo> php exakat.phar project -p <your project name>
The default report is the HTML report, called ‘Ambassador’. You’ll find it in ./projects/<your project name>/report.
Other reports, build with ‘report’ command, will also be saved there, with different names.
There are several ways to do that : use symbolic links, make a copy of the source.
php exakat.phar init -p <your project name> -R <path/to/the/code> -symlink php exakat.phar init -p <your project name> -R <path/to/the/code> -copy php exakat.phar init -p <your project name> -R <path/to/the/code> -git
Symlink will branch exakat directly into the code; -copy makes a copy of the code (this means the code will never be updated without manual intervention); git (or other vcs) may also be used with local repositories.
Exakat do not modify any existing source code : it only access it for reading purpose, then works on a separated database. As a defensive security measure, we suggest that exakat should work on a read-only copy of the code.
Yes. After initing a project, open the projects/<project name>/config.ini file, and update the ignore_dir line. For example, to ignore a behat test folder, and to ignore any file called ‘license’ :
ignore_dir = '/behat/'; ignore_dir = 'license';
You may also include files, by using the include_dir line. Including files is processed after ignoring them, so you may include files in folders that were previously ignored.
It is recommended to run exakat with PHP 7.0 and more recent. Older version are not so well tested, since they have reached their end of life.
Note that you may test your code on PHP 5.x, while running Exakat on PHP 7.0. There are 2 distinct configuration options in Exakat. ‘php’ is the path to the PHP binary that runs Exakat : this one should be PHP 7.0+. ‘phpxx’ are the path to the PHP helpers, that are used to tokenized and lint the target PHP code. This is where PHP 5.x may be configured.
; where and which PHP executable are available php = /usr/local/sbin/php71 php52 = php53 = /usr/local/sbin/php53 php54 = php55 = php56 = php70 = php71 = php72 =
Above is an example of a exakat configuration file, where Exakat is run with PHP 7.1 and process code with PHP 5.3.
This error is displayed when the host machine doesn’t have Ansible installed. Install ansible, and try again to provision.
Currently, Windows is not supported, though it might be some day.
Until then, you may run Exakat with Vagrant, or with Docker.
When run from the sources, Exakat has everything it needs to fulfill its mission. There is no central server that does the job, and requires the transmission of the code.
When running an audit on the Saas service of Exakat, the code is processed on our servers.