Custom extensions for Phabricator.

= Development = The best way to develop Phlab is to use Docker Compose locally by running docker-compose up from the root of the repository. Before doing so, you should have the following repositories cloned locally, in the same parent directory as Phlab itself:

• Arcanist
• libphutil
• Phabricator

Phabricator requires that it is accessed with a Host header containing a period (see T2433: Move the "no dots in domain" setup check to pre-install) and so you will not be able to access Phabricator via http://localhost. Instead, you should add 127.0.0.1 phabricator.local to /etc/hosts and access Phabricator via http://phabricator.local.

Nginx has been configured to bind to port 80 by default. You can bind to an alternative port by setting the HTTP_PORT environment variable.

== Unit tests == To run unit tests:

~/freelancer-dev/phlab > docker-compose up

# in a separate shell
~/freelancer-dev/phlab > docker exec -it phlab_worker_1 /bin/bash
root@ff02e67a5471:/# cd /usr/local/src/phlab/
root@ff02e67a5471:/usr/local/src/phlab# ../arcanist/bin/arc unit src/*

Unit tests can only be ran inside the container that docker spins up so you will need to run arc diff --nounit when creating a differential revision

== Troubleshooting == During local development, the db can get corrupted. When this happens, you can run docker-compose down --volumes to stop and remove containers, networks and volumes created by docker-compose up.