- 14 Aug, 2020 1 commit
-
-
Łukasz Nowak authored
-
- 13 Aug, 2020 2 commits
-
-
Łukasz Nowak authored
Interesting HTTP server from https://h2o.examp1e.net/
-
Łukasz Nowak authored
Some tests are checking deeply that bootstrap script works correctly inside if prepared VM, but those prepared VMs are big chunks of data to be fetched, so it's required to wait quite long.
-
- 12 Aug, 2020 1 commit
-
-
Rafael Monnerat authored
This contains data for running tests on Upgrade
-
- 11 Aug, 2020 1 commit
-
-
Julien Muchembled authored
-
- 10 Aug, 2020 1 commit
-
-
Łukasz Nowak authored
-
- 07 Aug, 2020 6 commits
-
-
Thomas Gambier authored
This reverts 80af2841 and b4f83dd0. We will force to compile gcc only in the machine preparing the source but not in the OBS machines actually compiling the packages.
-
Thomas Gambier authored
-
Thomas Gambier authored
The PYTHON variable is used in Makefile (https://gitlab.gnome.org/GNOME/glib/-/blob/2.58.3/glib/Makefile.am#L463) to generate the shebang for script gtester-report. With component/defaults.cfg, we have PYTHON=python2.7 so the shebang become '#!python2.7' which is an error for building a package on Fedora/SUSE: [ 3269s] *** ERROR: ./opt/slapos/parts/glib/bin/gtester-report has shebang which doesn't start with '/' (python2.7) The simplest solution is to remove this tester script as it is not needed and have been removed in newer version of glib already. This patch can thus be reverted when upgrading glib version.
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Jérome Perrin authored
Introduce an [editorconfig] configuration file to tell developer editors that we want an empty line at end of file. After making softwares and component uses a buildout.hash.cfg file, run [eclint] fix to apply the style. eclint is also added in the commit hooks (that one can install with `npm install` from the root of this repository) [editorconfig]: https://editorconfig.org/ [eclint]: https://github.com/jedmao/eclint See merge request nexedi/slapos!757
-
- 06 Aug, 2020 1 commit
-
-
Łukasz Nowak authored
-
- 05 Aug, 2020 14 commits
-
-
Julien Muchembled authored
-
Jérome Perrin authored
It seems `eclint fix folder/file` sometimes dos not work, but `eclint fix folder/` worked.
-
Jérome Perrin authored
done with: npm install git ls-files | grep -v '\/unstable\/' | xargs ./node_modules/.bin/eclint fix git ls-files | grep buildout.hash.cfg | xargs ./update-hash
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
So that we all edit files in a consistent style
-
Jérome Perrin authored
Sometimes, gitlab and qemu are reported by software release tests to link against libcap-ng and libzma from system. This happens when the development packages are installed on the system. Approach here is to build with slapos version of the libraries. See merge request !789
-
Jérome Perrin authored
Using an script to set the environment is easier to use, but the main reason is that if we want to be able to use shared part from outer slapos (like when using in theia or slaprunner), the working directory for test must be contained in the instance directory of the outer slapos, so that when we run slapos node prune in the outer slapos this command can see that shared parts are used.
-
- 03 Aug, 2020 5 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
This was using zlib and lzma from system if they are available, so we tell bundler to use the slapos version. We have to use both in --with-cflags for nokogiri itself and as CFLAGS environ for when nokogiri build its included libxml2
-
Jérome Perrin authored
don't let configure autodetect and build something different depending on the presence of this library on the host system
-
Jérome Perrin authored
Explicitly build with libcap-ng instead of depending on presence of the development library on the host. Also fix the way of disabling tinfo, there was warning at the end of configure saying this option is not used
-
Jérome Perrin authored
-
- 02 Aug, 2020 1 commit
-
-
Julien Muchembled authored
-
- 30 Jul, 2020 6 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Backend logs are exposed as usual access and error logs. By using rsyslogd templates and regex filtering, the rsyslogd reacts itself and creates needed files per each slave which accesses it. Thanks to this, it's configuration is static from point of view of SlapOS profiles, and can be generated once. As the rsyslogd configuration became fully special to backend-haproxy, the rsyslogd template filename and its references has been correctly renamed.
-
Łukasz Nowak authored
Logs are critical for caddy-frontend, so let's configure rotate-num locally, as changes in the stack can come unattended, and can result with loosing logs.
-
Łukasz Nowak authored
We moved out from local logrotate configuration long time ago, it was just leftover.
-
Łukasz Nowak authored
haproxy by itself provides good information, so there is no need to add information from rsyslogd itself.
-
Łukasz Nowak authored
The logrotate folder also serves as an publication folder for logs, so be sure that logs are linked there.
-
- 28 Jul, 2020 1 commit
-
-
Łukasz Nowak authored
While building haproxy on one machine, and using it on another, the CPU optimisations can lead to haproxy not working at all on other CPUs. In context of SlapOS packages are distributed in binary form, so haproxy binary has to support all CPUs.
-