• Sorry for the WoT, it’s kind of complex (for me)
  • What you need to do is a mixture of the advanced and the “normal” install guide, and a bit of guesswork
  • Phacility probably does not endorse this installation style, but I hope it will work and survive


Sources of information for this topic:



  • Ubuntu 14.04 LTS installed and updated on phserver
  • MySQL >= 5.5 running on mysqlserver
  • have SSL certificate and corresponding key for phab1.your.domain ready (in your homedir ~)



  • new Phabricator instance will be called phab1
  • MySQL is not on the same machine
  • You’re logged in to phserver as a user with sudo privileges


Work steps:

  • install “standard” software (if new server)
  • create an instance directory
  • create an apache site file
  • paste the following content
  • install certificates by copying them to their destinations
  • install Phabricator components
  • this will have created three directories below /var/www/phab1/: arcanist, libphutil and phabricator
  • enable the apache site
  • restart apache
  • create a mysql user phab1 on mysqlserver
  • grant that user full access to all of his (not yet existing) databases
  • working on the console, you must have an environment variable indicating the instance you want to work with
  • create /var/www/phab1/phabricator/conf/custom/phab1.conf.php (no closing php tag is intentional)

  • set the storage namespace for this instance, so that database names start with phab1_. The -E parameter is important for passing environment variables to sudo.
  • the file /var/www/phab1/phabricator/conf/local/local.json should now look like this:
  • make the instance directory owned by the web server
  • install Phabricator databases and schemas
  • this will create all needed databases, and apply patches to them directly. Reply to questions with “y”
  • now visit https://phab1.your.domain/ with your browser and create an admin user
  • after that, Phabricator will show the Setup issues page (/config/issue/) with all tasks that need to be completed before you’re finally ready.
  • one of the tasks says that “Phabricator daemons are not running”. Create /etc/init/phab1-phd.conf:
  • create daemon working directories
  • set Phabricator daemon working directories
  • start Phabricator daemons

After these steps you should have a working instance of Phabricator, that works independantly from other instances on that same machine, except for using the same web server. What I cannot say at the moment, is whether all Phabricator modules will work smoothly this way. I hope they all respect the environament variables and/or the custom settings. One of the most vital things for working with this setup, especially when setting config values on the console, is to use the -E parameter. The path from where scripts or binaries (phd f.e.) are started also plays a role.

We went this way because we didn’t want to throw a new VM at each instance. A different way of addressing this could be to put Phabricator in a container, but this is beyond my scope currently. I hope this will turn out to be a working solution. Comments welcome.