Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-04-24 | take out plain couchdb setup, always deploy bigcouch (Feature #2176) | varac | |
2013-04-24 | Use pre-salted+hashed admin pw for couchdb (Feature #1941) | varac | |
2013-04-24 | updated needed couchdb users and DBs | varac | |
2013-04-24 | Use pre-salted+hashed user pw for couchdb (Feature #2324) | varac | |
2013-04-04 | add Erlang Distributed Node Protocol Port json entry under bigcouch | Micah Anderson | |
setup ednp_server and ednp_client stunnels update couchdb puppet submodule to support configurable ednp_port parameter and general module cleanup pass ednp_port to couchdb setup so that it is configured in the vm.args template clarify in comments the difference between the epmd and ednp ports remove hard-coded erlang_vm_port variable and instead setup shorewall to allow for the stunnel connection only setup dnat rules for the ednp client connections | |||
2013-04-04 | remove the apache_ssl_proxy cleanup | Micah Anderson | |
2013-04-02 | couchdb hosts include site_shorewall::couchdb::bigcouch | varac | |
2013-03-14 | add couchdb stunnel server | Micah Anderson | |
2013-03-14 | remove apache ssl proxy in preparation of replacing it with a stunnel setup | Micah 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-14 | include cloudant package repo for bigcouch server | varac | |
2013-03-10 | pass couchdb cookie to class couchdb | varac | |
2013-03-10 | use bigcouch in site_couchdb | varac | |
2013-02-06 | include shorewall config for webapp and couchdb | varac | |
2013-01-31 | tag 'base' is a bad idea because it invokes apache::base as well | varac | |
2013-01-31 | tag 'service' for all service classes | varac | |
2012-12-07 | new names for couchdb DBs | varac | |
2012-12-07 | removed pinning couchdb to unstable because 1.2.0-3 is in wheezy, finally | varac | |
2012-11-22 | call refresh_apt before installing couchdb, solves ↵ | varac | |
https://leap.se/code/issues/994 | |||
2012-11-06 | adopt new hiera creditials | varac | |
2012-11-04 | working resource relationships for deployment | varac | |
2012-11-03 | install apache_ssl_proxy, add users, create DBs + security roles | varac | |
2012-11-03 | deploy server_cert.pem + server_key.pem, notify apache | varac | |
2012-11-03 | overwrite /etc/apache2/ports.conf so 0-default.conf and 0-default_ssl.conf ↵ | varac | |
don't start on port 80/443 | |||
2012-11-03 | configure apache ssl proxy for couchdb | varac | |
2012-11-01 | use couchdb x509 hiera values | varac | |
2012-11-01 | deploy ssl cert working | varac | |
2012-11-01 | deploy ssl certs | varac | |
2012-11-01 | another try of class relationships | varac | |
2012-10-30 | try explicit class relation | varac | |
2012-10-30 | configure unstable pinning for couchdb before install | varac | |
2012-10-13 | install couchdb from unstable, see init.pp | varac | |
2012-10-13 | use site_couchdb | varac | |
2012-10-13 | use debian unstable for couchdb | varac | |