1
0
mirror of https://github.com/ohwgiles/laminar.git synced 2024-10-27 20:34:20 +00:00
Go to file
[[sroracle]] 1642899159 test: fix RunTest on systems with single file core utilities (#95)
On systems such as Alpine Linux (with busybox) and Adelie Linux (with
coreutils), the shell core utilities such as pwd, true, false, env, and
yes are all symlinks to a single binary. This single binary relies on
the name of the symlink to determine which command ("applet" in busybox
parlance) to execute. Therefore creating symlinks to these symlinks will
not work since the single binary will only see the top-level symlink and
thus think it is an invalid command.

Instead, generate executable shell scripts that exec into the desired
command. This also allows $PATH based resolution to occur instead of
hard-coding the command paths.

See also issue #94.
2019-05-24 21:27:24 +03:00
etc resolves #85: systemd unit file After=network.target 2019-03-31 08:36:08 +03:00
example-scripts quote args to xsltproc 2015-09-20 09:23:50 +02:00
src log.h: null-terminate compile-time filename strings 2019-04-17 09:26:45 +03:00
test test: fix RunTest on systems with single file core utilities (#95) 2019-05-24 21:27:24 +03:00
CMakeLists.txt resolves #80: reverse-proxy with custom base URL 2019-03-29 22:43:16 +03:00
COPYING Added GPLv3 license file. 2017-10-11 09:56:26 +02:00
docker-build-centos.sh Install bash/zsh completions in correct locations 2018-10-16 20:38:48 +03:00
docker-build-debian.sh Install bash/zsh completions in correct locations 2018-10-16 20:38:48 +03:00
docker-xbuild-debian-armhf.sh resolves #73: script to build Raspbian package 2018-11-30 15:56:22 +02:00
README.md minor README tweaks: use https in links and add badge 2018-10-16 20:47:10 +03:00
UserManual.md laminarc: more explicit return codes 2019-04-11 21:00:00 +03:00

Laminar CI status

Laminar (https://laminar.ohwg.net) is a lightweight and modular Continuous Integration service for Linux. It is self-hosted and developer-friendly, eschewing a configuration UI in favour of simple version-controllable configuration files and scripts.

Laminar encourages the use of existing GNU/Linux tools such as bash and cron instead of reinventing them.

Although the status and progress front-end is very user-friendly, administering a Laminar instance requires writing shell scripts and manually editing configuration files. That being said, there is nothing esoteric here and the guide should be straightforward for anyone with even very basic Linux server administration experience.

See the website and the documentation for more information.

Building from source

First install development packages for capnproto (version 0.7.0 or newer), rapidjson, sqlite and boost (for the header-only multi_index_container library) from your distribution's repository or other source. Then:

git clone https://github.com/ohwgiles/laminar.git
cd laminar
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/
make -j4
sudo make install

make install includes a systemd unit file. If you intend to use it, consider creating a new user laminar or modifying the user specified in the unit file.