summaryrefslogtreecommitdiff
path: root/puppet/modules/site_couchdb/manifests/init.pp
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-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
2012-12-07new names for couchdb DBsvarac
2012-12-07removed pinning couchdb to unstable because 1.2.0-3 is in wheezy, finallyvarac
2012-11-22call refresh_apt before installing couchdb, solves ↵varac
https://leap.se/code/issues/994
2012-11-06adopt new hiera creditialsvarac
2012-11-04working resource relationships for deploymentvarac
2012-11-03install apache_ssl_proxy, add users, create DBs + security rolesvarac
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-01use couchdb x509 hiera valuesvarac
2012-11-01deploy ssl cert workingvarac
2012-11-01deploy ssl certsvarac
2012-11-01another try of class relationshipsvarac
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