- 29 Jan, 2021 1 commit
-
-
Łukasz Nowak authored
-
- 28 Jan, 2021 3 commits
-
-
Kazuhiko Shiozaki authored
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Fixes: * fail fast in case of trouble * treat 1.0 as special working branch and be ok to remove it * select origin/1.0 as source of the local 1.0 branch Thank to this it can be used in clean repository.
-
- 27 Jan, 2021 5 commits
-
-
Łukasz Nowak authored
Fixes: * fail fast in case of trouble * treat 1.0 as special working branch and be ok to remove it * select origin/1.0 as source of the local 1.0 branch Thank to this it can be used in clean repository.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Thanks to shacache it will be cached anyway, and it allows to easily refer to the source changes and eventual discussion.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
- 26 Jan, 2021 8 commits
-
-
Łukasz Nowak authored
Since Jinja 2.11 it's possible to do nice tests against true, false and others, which is important for various type checks.
-
Łukasz Nowak authored
Since "caddy-frontend: Switch monitor ports to internal use" monitor ports are internal usage only and this test is obsolete.
-
Łukasz Nowak authored
It's not used at all in current approach.
-
Łukasz Nowak authored
The public-ipv4 comes from the historical usage of the system, but since new implementation came into place it was never needed, so now it's time to say goodbye. Test has been updated to do in-house mimic of the used IP to access.
-
Łukasz Nowak authored
It's from old approach, which is not going to be implemented.
-
Łukasz Nowak authored
Since recent change the virtualhostroot-https-port and virtualhostroot-http-port are casted to integer during configuration generation so it's require to validate this input and reject incorrect values.
-
Łukasz Nowak authored
As decision making quite often requires access to more than one slave entry, it's better to keep the logic above configuration generation. Also configuration generation is already complex, and it's better to have it simplified, especially in case of switching the component. Use already prepared values from apache-custom-slave-list.cfg.in in default-virtualhost.conf.in to simplify even more. Pass variables to the other profiles without casting them to string, so that they work out of the box.
-
Jérome Perrin authored
Following up !858 to support milliseconds timings in access logs
-
- 25 Jan, 2021 3 commits
-
-
Xavier Thompson authored
-
Vincent Pelletier authored
Remove unused "plugin" entry. Add locally-referenced-but-defined-by-another-file "bin".
-
Vincent Pelletier authored
Should have been part of: commit c787d04c Author: Hardik Juneja <hardik.juneja@nexedi.com> Date: Thu Jun 8 18:39:28 2017 +0200 remove unnecessary monitor_template section form erp5 stack
-
- 22 Jan, 2021 1 commit
-
-
Xavier Thompson authored
-
- 21 Jan, 2021 1 commit
-
-
Jérome Perrin authored
Since bd3c2b18 (Remove httpd from ERP5 and use haproxy instead, 2020-12-14) timing in balancer access log files are in milliseconds, no longer in microseconds as they use to be with apache. We update apachedex to version 1.8, where it supports generating reports from access log files with milliseconds, as long as the expected format is passed with --logformat argument. We changed the default value of apachedex configuration to use the expected --logformat argument, but users with a custom apachedex config passed as instance parameters (monitor.apachedex-configuration) will have to update their request parameters, to also pass --logformat. Since this is breaking change, we take this opportunity to introduce another breaking change, this parameter is not longer a string with all arguments on the same line, which was problematic because these arguments contained quotes and backslashes. The arguments are now passed as a list of strings which will become the list of arguments passed to apachedex. This is implemented by generating an apachedex config file, which simplifies the generation of the wrapper. For this we also needed to upate slapos.toolbox. The same change is reflected to the overriden profiles in slapos-master, but for slapos-master we don't pass the --logformat argument, because slapos-master is using httpd, so the logs timings are still in microseconds.
-
- 20 Jan, 2021 2 commits
-
-
Łukasz Nowak authored
90 bugs fixed since 2.0.17: * 6 major * 30 medium * 54 minor See http://www.haproxy.org/bugs/bugs-2.0.17.html
-
Jérome Perrin authored
-
- 19 Jan, 2021 3 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Thanks to work on TrafficServer bug 7425 it was possible to understand correctly the switches and setup ATS to SlapOS CDN needs. max_stale_age with negative_revalidating_enabled is used to simulate stale-if-error and negative_revalidating_lifetime is set to 0, as Expires header provided by this switch is needless in SlapOS case. Tests are updated to follow the real use case, by rewriting ATS configuration to meet times required for the test to finish in reasonable time.
-
Jérome Perrin authored
Update to 1.9.0 ( https://github.com/eclipse-theia/theia/blob/v1.9.0/CHANGELOG.md#v190---16122020 ) Update extensions to newer version and to the URLs from openvsx instead of github, since openvsx prevent maintainers to modify releases. Also use buildout directly to download extensions, so that we verify signatures and have possibility to use cache See merge request nexedi/slapos!873
-
- 18 Jan, 2021 1 commit
-
-
Xavier Thompson authored
See merge request nexedi/slapos!886
-
- 15 Jan, 2021 4 commits
-
-
Xavier Thompson authored
-
Łukasz Nowak authored
-
Kazuhiko Shiozaki authored
In reality, proxy.config.http.cache.max_stale_age was used for stale cache lifetime in current ATS implementation. Thus we increase proxy.config.http.negative_revalidating_lifetime value to the same value as proxy.config.http.cache.max_stale_age whose default is 604800.
-
Łukasz Nowak authored
-
- 14 Jan, 2021 1 commit
-
-
Cédric Le Ninivin authored
-
- 13 Jan, 2021 5 commits
-
-
Xavier Thompson authored
-
Thomas Gambier authored
See merge request !887
-
Xavier Thompson authored
-
Jérome Perrin authored
We want the tests to use the code from the repository, but when we have a pinned version, buildout will use the code from repository only when the version from the repository match the version spec from the pin. The way slapos.recipe.template was pinned to 4.4 caused issues when we made a change in slapos.recipe.template to make it 4.5, because tests were no longer using code from slapos.recipe.template repository, but from 4.4 egg from pypi. To prevent this kind of issues, unset the slapos.recipe.template = 4.4 version pin and also unset the version for all tested egg, to prevent similar issues if extended profiles also have version pins.
-
- 12 Jan, 2021 2 commits
-
-
Xavier Thompson authored
See merge request nexedi/slapos!876
-
Xavier Thompson authored
-