RETIRED, Puppet module for phabricator

Go to file

Jeremy Stanley 06bfcaa60e Run database migrations when necessary Check the output of the `storage status` command for appearance of "Not Applied" migrations, and run an upgrade if so. This works around an earlier assumption that the command would exit nonzero when there are pending migrations, but it seems to exit zero even under those conditions. Change-Id: I5ff8026bfaaf31c8abcd55efc217256605be9e73		2016-12-19 19:22:30 +00:00
manifests	Run database migrations when necessary	2016-12-19 19:22:30 +00:00
spec	Fix target path for regular git clone during tests	2015-08-19 16:40:52 -07:00
templates	Correct certificates class name in vhost template	2016-11-16 22:22:41 +00:00
.gitignore	Patches Required to Deliver Pholio	2016-08-31 10:06:44 +10:00
.gitreview	Add .gitreview file	2015-07-14 15:16:19 -04:00
Gemfile	Use new infra_spec_helper for gem dependencies	2016-06-21 18:39:38 -07:00
README.rst	Initial commit	2015-04-01 17:10:52 -04:00
Rakefile	Make the linter happy	2015-04-01 18:26:28 -07:00

README.rst

puppet-phabricator =================

A puppet module for installing and managing a phabricator instance. This is derived greatly from http://github.com/bloomberg/phabricator-tools

some notes for now:

This module should not manage a MySQL or a mail server itself - it should assume that those have been set up by other modules.

We want to put all config customizations into local.json and not into the database.

The initial.db file is from bloomberg, I'm not sure it's all that useful to folks.

We still need to do this in my.cnf :

sql_mode=STRICT_ALL_TABLES
ft_stopword_file=/phabricator/instances/dev/phabricator/resources/sql/stopwords.txt
ft_min_word_len=3
ft_boolean_syntax=' |-><()~*:""&^'
innodb_buffer_pool_size=600M

then do:

REPAIR TABLE phabricator_search.search_documentfield;

I did not do: https://secure.phabricator.com/book/phabricator/article/configuring_file_domain/ yet, or really think about it.

I also have not made puppet do anything with:

sudo /phabricator/instances/dev/phabricator/bin/phd start

Which are the background daemons.

storyboard migration

The data migration script assumes a storyboard schema in the same mysql server as the phabricator schemas. It sets up users for everyone in storyboard with a password of admin. We'll be doing openid/oauth eventually, so I didn't spend a ton of time on that.

The apps that are disabled are disabled on purpose.