opendev
/
puppet-phabricator
Code Issues Proposed changes
RETIRED, Puppet module for phabricator
42 Commits 1 Branch 0 Tags 341 KiB
Go to file
Colleen Murphy 92a27b18c3 Update Gemfile for Zuulv3 
The logic in the Gemfile was relying on Zuulv2 variables to find out
whether the spec helper gem was already available on disk, and since
Zuulv3 has changed things it was failing to find it and downloading the
master version instead. This patch ensures the Gemfile looks for the gem
in the right place when running in CI.

Change-Id: I74fd209d1b8257ebd146e50fa36fda8ceecc4e03
 		2018-07-12 09:57:45 +02:00
manifests Fix beaker on xenial 2017-06-24 16:33:30 +02:00
spec/acceptance/nodesets Depend on helper gem for spec_helper_acceptance 2017-08-18 10:41:44 +02: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 Update Gemfile for Zuulv3 2018-07-12 09:57:45 +02: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.