An error occurred fetching the project authors.
- 06 Sep, 2018 1 commit
-
-
Łukasz Nowak authored
-
- 31 Jul, 2018 1 commit
-
-
Łukasz Nowak authored
Features: * jinja2 is used to generate instance templates * downloads are done the same way for all resources * create with shared content for all instance profiles * fill in instance-common with shared sections * render templates late in order to ease its extenension and development * drop not needd duplicated section * drop slap-parameter in frontend and replicate template * simplify monitor configuration * move instance-parameter to instance file Thanks to this only one and topmost profile is reponsible for parsing and passing through the information which comes from the network
-
- 27 Jul, 2018 1 commit
-
-
Łukasz Nowak authored
The backend url can come from request in `url` and `https-url` strings. It is validated using real caddy template configuration and by using caddy's `-stdin`. It results with calling it on each slave having any of those parameters.
-
- 12 Jul, 2018 2 commits
-
-
Łukasz Nowak authored
In those places caddy_custom_https (and it's backward compatbility companion apache_custom_https) was not checked, thus making it impossible to just use https customisation, without http one.
-
Łukasz Nowak authored
caddy_custom_http and caddy_custom_https are implemented and exposed instead of apache_custom_http and apache_custom_https, but with backward compatbility for the latter form from apache-frontend. In TODO mark missing usage of custom http found during work on this commit.
-
- 03 Jul, 2018 1 commit
-
-
Łukasz Nowak authored
Therte is no need to control whitespace adding by Jijna2 and dropping it simplifies the templates. It will allow to take better control over generated configuration files.
-
- 28 Jun, 2018 5 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
As there is some kind of "collision" with request, allow to override parameters. Treat `<key>` as default and overwrite it with `frontend-config-<num>-<key>`, instead of having the global `<key>` always passed to slaves. This allows to request the partition with: monitor-httpd-frontend=12345 -frontend-config-1-monitor-httpd-frontend=9876 -frontend-config-1-monitor-httpd-frontend=8765
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Those kept are backward compatibility variables from the request.
-
Łukasz Nowak authored
This will make it easier to track changes.
-
- 27 Apr, 2018 1 commit
-
-
Alain Takoudjou authored
-
- 05 Jun, 2017 1 commit
-
-
Hardik Juneja authored
/reviewed-on !175
-
- 26 May, 2016 1 commit
-
-
Rafael Monnerat authored
-
- 21 Apr, 2016 1 commit
-
-
Rafael Monnerat authored
-
- 09 Dec, 2015 1 commit
-
-
Rafael Monnerat authored
-
- 08 Dec, 2015 1 commit
-
-
Alain Takoudjou authored
-
- 19 Nov, 2014 1 commit
-
-
Julien Muchembled authored
-
- 15 Sep, 2014 1 commit
-
-
Cédric Le Ninivin authored
-
- 08 Aug, 2014 2 commits
-
-
Cédric Le Ninivin authored
-
Cédric Le Ninivin authored
apache-frontend: update documentation for per frontend configuration
-
- 21 Jul, 2014 1 commit
-
-
Cédric Le Ninivin authored
-
- 03 Jul, 2014 1 commit
-
-
Cédric Le Ninivin authored
-
- 02 Jul, 2014 1 commit
-
-
Cédric Le Ninivin authored
-
- 21 May, 2014 1 commit
-
-
Cédric Le Ninivin authored
-
- 09 Dec, 2013 1 commit
-
-
Cédric Le Ninivin authored
-
- 30 Aug, 2013 4 commits
-
-
Cédric Le Ninivin authored
-
Cédric Le Ninivin authored
-
Cédric Le Ninivin authored
if you provide the parameter "-sla-i-foo", the sla parameter foo is used with the given value for the request of the i^th frontend
-
Cédric Le Ninivin authored
This commit introduce the "replicate" software type. The main instance of type replicate will request frontend and transmit to them all the needed configuration so that it seems transparent.
-