It is used internally for communication between backend and the server.

mpm-watchdog promise is not applicable for Caddy.

404 is served with notfound.html

Those kept are backward compatibility variables from the request.

Caddy is able to bind only to all or one interface
( https://github.com/mholt/caddy/issues/864 )

By using 6tunnel this limitation is workarounded, and in the result listen on IPv6.

Also drop needless "ipv6" keys across configuration.

As the the feature ssl_proxy_ca_crt is not implemented serve immediately
501 Not Implemented.

As the the feature ssl_proxy_ca_crt is not implemented serve immediately
501 Not Implemented.

%2F%2F is used to avoid double slashes cleanup with Caddy. See
https://github.com/mholt/caddy/issues/1298, which touches the problem,
but not enough for zope.

Features:

 * shared place for Caddy configuration
 * gather a lot of parameters for caddy executable, as dislike Apache
   Caddy is configured from command line
 * dummy vhost for example.org
 * challanges (ACME SSL) are disabled
 * bind to interfaces are done per site
 * cache access is dummy, but working
 * /server-status redone in Caddy style
 * antiloris dropped, as this is apache specific
 * apache_custom_http and apache_custom_https
 * dropped not needed leftover access-control-string and protected-path
 * nginx replacement added
 * bin/caddy-wrapper is provided in order to allow parameterization of caddy
   over the network
 * access to log files over http is provided
   * username on log access is consistent, it is not uppercased like it was
     originally on apache-frontend
 * list of TODOs in TODO.rst

This will make it easier to track changes.

Based on caddy-frontend tests

Features:

 * forcediphttpsadapter for SNI
 * compatbile with apache-frontend SR
 * local server to test against
 * supervisor state checks
 * promise list checks
 * test data (to save/load textual assertions)
 * own root CA for HTTPs backend

Based on Jerome's work from /software/proftpd/test/utils.py

Main changes:

 * tearDownClass is called in case of errors in setUpClass (mimic addCleanup
   instance method)
 * the setUpClass is split to smaller methods for ease of further development
 * full instance path is exposed for test introspection
 * software path of master partition is exposed for test introspection

proxy.timeout is provided

In order to follow proper way, move caddy to the component and reuse it.

  The webrunner user don't necessary uses webrunner to develop slapos,
  he can use webrunner to develop a new component, where instance is never
  created.

  If the software release don't instantiate instances, skip from continue and consider
  the restauration job done (data is copied, software is built).

 Once the requests to cloudooo software types were removed,
 orphan instances might be kept arround due a lack of implementation
 of garbage collection on slapos proxy.

 This change allows the ghost cloudooo instances, don't fail, until
 the garbage collection implementation be deployed, reducing the
 number of irrelevant failures on resilience after an upgrade.

Requirement for nexedi/erp5!695

/reviewed-on nexedi/slapos!343

jinja2 template is required, as some paramters might come from the network.

/reviewed-on nexedi/slapos!345

/reviewed-on nexedi/slapos!346

Filename is split as an URL path, and joined in OS-dependent manner.
Remove corresponding comment in all buildout.hash.cfg files.

This prevent outdated instances to fail resilience, so it makes this change backward compatible.

Do not upper filenames nor users, use them as is.

/reviewed-on !339

No custom_http nor custom_https shall publish information normally calculated.

/reviewed-on nexedi/slapos!340

This brings the following changes of git-backup:

	kirr/git-backup@0b8d834b...cc6ac54f

the most important of which is dramatical speedup of pull and 30-50%
speedup of restore if bitmap index of backup repo is built and git is
recent enough.

Please see the following commits for details:

	kirr/git-backup@899103bf
	kirr/git-backup@3efed898
	kirr/git-backup@0ab7bbb6

/cc @alain.takoudjou, @rafael, @jerome

/reviewed-on nexedi/slapos!342

Extended KVM SR does not have this hosts in allowed, and we need to stick
with it.

For reference in case if some existing Python distribution does not install,
it was detected with "git diff 8deeab.. -- stack/slapos.cfg"

The Debian packaging of our RINA kernel builds with GCC 4.9,
which is not available on Stretch:

  # apt install ./linux-build-deps_4.1.33+rina65.g2e1cdbcb4-1_amd64.deb
  ...
  The following packages have unmet dependencies:
  linux-build-deps : Depends: gcc-4.9 but it is not installable