summaryrefslogtreecommitdiff
path: root/puppet/modules/site_couchdb
AgeCommit message (Collapse)Author
2013-03-14add couchdb stunnel serverMicah Anderson
2013-03-14remove apache ssl proxy in preparation of replacing it with a stunnel setupMicah Anderson
This presents us with an interesting problem of deprecation. We need to manage the removal of something that we previously installed in any released code. How long we carry the puppet code that removes raises some interesting questions: do we require that someone who deployed version 1 (where the apache ssl proxy was deployed) of the platform upgrade first to version 2 (where we remove the apache ssl proxy) before they upgrade to version 3 (where the apache ssl proxy removal is no longer present) -- or do we allow people to skip versions?
2013-03-14include cloudant package repo for bigcouch servervarac
2013-03-10pass couchdb cookie to class couchdbvarac
2013-03-10use bigcouch in site_couchdbvarac
2013-03-10site_couchdb::configure moved to couchdbvarac
2013-03-10futon is enabled by default on bigcouch in default.inivarac
we need to find another way to disable futon, it won't work disabling it here
2013-03-09couchdb init file moved to couchdb modulevarac
2013-02-09re-enabling futon (see #1121)varac
2013-02-08couchdb: disable futon (Feature #1121)varac
2013-02-06include shorewall config for webapp and couchdbvarac
2013-01-31tag 'base' is a bad idea because it invokes apache::base as wellvarac
2013-01-31tag 'service' for all service classesvarac
2013-01-29eliminate dynamic lookup deprecation warnings for site_couchdb::apache_ssl_proxyMicah Anderson
2012-12-19added ca_daemon initscript for latervarac
2012-12-10couchdb: use x509 module to deploy certs (fixes #1063)varac
2012-12-07new names for couchdb DBsvarac
2012-12-07removed pinning couchdb to unstable because 1.2.0-3 is in wheezy, finallyvarac
2012-12-04remove no longer needed removal of the ports.conf fileMicah Anderson
2012-12-04alphabetize the apache modulesMicah Anderson
2012-12-04Stop the [warn] NameVirtualHost *:443 has no VirtualHosts errorsMicah Anderson
When we include apache::ssl it ships the ssl.conf file which sets up the NameVirtualHost *:443, so we just do what that class does fixes: https://leap.se/code/issues/944
2012-11-22call refresh_apt before installing couchdb, solves ↵varac
https://leap.se/code/issues/994
2012-11-08 = truevarac
2012-11-06adopt new hiera creditialsvarac
2012-11-06sleep some more after couchdb restart, adopt new hiera creditialsvarac
2012-11-04working resource relationships for deploymentvarac
2012-11-04deploy couchdb initscript, restart couchdb after config file changevarac
2012-11-04provide coustom couchdb initscript to ensure stop/restart is workingvarac
2012-11-03added apache_ssl_proxy.ppvarac
2012-11-03install apache_ssl_proxy, add users, create DBs + security rolesvarac
2012-11-03query hiera adminpw in site_couchdbvarac
2012-11-03deploy server_cert.pem + server_key.pem, notify apachevarac
2012-11-03overwrite /etc/apache2/ports.conf so 0-default.conf and 0-default_ssl.conf ↵varac
don't start on port 80/443
2012-11-03configure apache ssl proxy for couchdbvarac
2012-11-03[admins] section moved to local.d/admin.inivarac
2012-11-03added local.d/admin.ini to set admin pwvarac
2012-11-01use couchdb x509 hiera valuesvarac
2012-11-01deploy ssl cert workingvarac
2012-11-01deploy ssl certsvarac
2012-11-01custom local.ini with ssl supportvarac
2012-11-01another try of class relationshipsvarac
2012-10-30try explicit class relationvarac
2012-10-30try explicit class relationvarac
2012-10-30configure unstable pinning for couchdb before installvarac
2012-10-13install couchdb from unstable, see init.ppvarac
2012-10-13use site_couchdbvarac
2012-10-13use debian unstable for couchdbvarac