Age | Commit message (Collapse) | Author |
|
develop
|
|
METH_POST probably does not catch PUT, DESTROY etc. So instead we
now use the master as the default and only use the replications
for GET and HEAD requests.
|
|
|
|
|
|
- See issue #5217
- See companion change in leap_web
|
|
|
|
|
|
|
|
|
|
|
|
If obfsproxy is spawned alongside eip service, make it listen to
the gateway_adress IP. If obfsproxy is running standalone listen
to ip_address.
|
|
|
|
|
|
|
|
|
|
|
|
log_level sets minimum logging severity of obfsproxy daemon, can
be error, warning, info, debug. Defaults to info.
|
|
Create obfsproxy directory in /var/log, specify log file when
obfsproxy is spawned by init script, create a logrotate
configuration for obfsproxy's logs.
|
|
|
|
|
|
|
|
|
|
|
|
Also clean up a little the obfsproxy puppet class, create appropriate
directories, restrict permissions.
|
|
|
|
|
|
now "hostname -f" results in the correct hostname.
Fixes #5835
|
|
|
|
|
|
This only works with the latest patch to puppet_couchdb
|
|
|
|
|
|
|
|
|
|
|
|
out into separate files.
|
|
needed shorewall will be automatically set up. requires new leap_cli
|
|
|
|
|
|
|
|
|
|
|
|
depending on the services.
|
|
|
|
the problem was following:
if a host has the webapp service, the template for /etc/hosts adds some stuff.
But setup.pp did not ask hiera about the services so
"/srv/leap/bin/puppet_command set_hostname" always resets the hostname.
Since that gets triggered every time you run "leap deploy" the
hostname changes, some services restart, then the hostname changes back and
the services restart again.
The solution is to get the hiera data before every run.
|
|
|
|
|
|
|
|
|
|
|