- 11 Nov, 2022 1 commit
-
-
Jérome Perrin authored
In some cases, for example when the instance does not have internet access, or to speed up slapos node instance, it's better not to have frontend requests in the embedded slapos. In this case, the default slapos proxy behavior of returning a "fake frontend" [1] will apply and promises checking frontend status will pass anyway. [1]: see slapos.core commit 2a53efca2 (proxy: bypass simple fronten requests by returning URL, 2019-03-25)
-
- 10 Nov, 2022 16 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
bring fixes for about 20 CVE
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
slapos.cookbook:haproxy no longer exist
-
Jérome Perrin authored
See merge request !1278
-
Jérome Perrin authored
-
Jérome Perrin authored
Put broken python interpreters in path so that fail if they try to use system python
-
Jérome Perrin authored
-
Jérome Perrin authored
We should not use $PYTHON, because this implicitly depends on the python version that was used when the shared part is installed, leading to this kind of problematic scenarios: - install the part from a python2.7 software, this creates scripts with "python2.7" in shebang line - install a python3 software referencing glib, it uses the shared part that was installed with python2, but "python2.7" is not in $PATH By referencing the part explicitly, it becomes part of the signature of the part, so a software on python2 and a software on python3 will use a different version of the shared part.
-
Jérome Perrin authored
945a2e97 (proxysql: bundled libinjection needs Python 2, 2021-12-23) addressed the problem that proxysql was using system python, by placing slapos' python in $PATH, but it added it after default $PATH, which made proxysql use system python if available and only fallback to slapos' python. This changes the order of $PATH entries to always use slapos' python
-
Jérome Perrin authored
python or python2 is system python, which we want to avoid
-
Ophélie Gagnard authored
-
- 09 Nov, 2022 1 commit
-
-
Ophélie Gagnard authored
-
- 08 Nov, 2022 2 commits
-
-
Ivan Tyagov authored
-
Xavier Thompson authored
-
- 07 Nov, 2022 6 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
with support for aborting query ( https://github.com/mroonga/mroonga/issues/344 )
-
Łukasz Nowak authored
Configuring failover URL and being able to rely on cached content is not so simple, thus document the requirement and prove in test, that such configuration works correctly.
-
Łukasz Nowak authored
Checking SLAPOS_TEST_DEBUG in the test itself came from ancient history of the testcase, it's time to drop it and use modern apporach.
-
Jérome Perrin authored
This includes xmlsec, the C library and its python bindings in ERP5, using the latest versions that are compatible with python 2. `1.3.9` is the latest version of the python bindings with python 2 support and `1.2.30` is the latest version of the C library compiling with this version of the python bindings. See merge request nexedi/slapos!1272
-
Vincent Pelletier authored
-
- 04 Nov, 2022 3 commits
-
-
Xavier Thompson authored
Since slapos.core!436 requesting with `--parameters-file` requires that a JSON schema exists at <sr-url>.json for the requested SR.
-
Romain Courteaud authored
Missing trailing / See nexedi/slapos@5e1ff2de
-
Joanne Hugé authored
-
- 03 Nov, 2022 1 commit
-
-
Levin Zimmermann authored
zlib source url has been moved. Please see issue https://github.com/madler/zlib/issues/649 for reference.
-
- 31 Oct, 2022 3 commits
-
-
Ivan Tyagov authored
See merge request nexedi/slapos!1276
-
Martin Manchev authored
-
Jérome Perrin authored
Co-authored-by: Kazuhiko SHIOZAKI <kazuhiko@nexedi.com>
-
- 25 Oct, 2022 1 commit
-
-
Joanne Hugé authored
-
- 24 Oct, 2022 3 commits
-
-
Joanne Hugé authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 19 Oct, 2022 3 commits
-
-
Joanne Hugé authored
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Running test as last makes no sense nowadays, as the site is fully prepared. Awaiting for each possible log of configured frontend is not worth the requirement, so make those tests as first ones, which simplifies running only them with reproducible effect. All tests which could be affected by that fact has been identified and changed.
-