./bin/aphlict start does not default to the correct configuration file after upgrading our install
This is due to the path to Phabricator being populated in a directory not named phabricator
Steps to reproduce:
- Populate Phabricator in a folder that is named 'htdocs', in our case /opt/bitnami/apps/phabricator/htdocs
- Run ./bin/aphlict start
I'm not sure why bitnami chose to do this when building the virtual appliance they distribute... but I also don't notice any documentation saying that the folder name is important either.
I can pass the --config option and it works just fine, and ./bin/config is not affected and finds conf/local/local.json as expected.
This seems to double up the "phabricator" folder name in this case.
Reading configuration from: phabricator/conf/aphlict/aphlict.default.json Usage Exception: Failed to read configuration file. File system entity '/opt/bitnami/apps/phabricator/phabricator/conf/aphlict/aphlict.default.json' does not exist.