You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Mike Swierczek a1a95c8e7f add pkg-config
6 days ago
docker cmake: more appropriate use of CMAKE_INSTALL_PREFIX 4 years ago
etc Have at least some minimal logging 1 year ago
examples nginx example: trailing slash on proxy_pass argument 2 years ago
pkg pkg: move to debian 11 (bullseye) 2 years ago
src Support Clang/LLVM build on FBSD 4 months ago
test test: assert on >= 5 rather than strictly == 2 years ago
CMakeLists.txt Support Clang/LLVM build on FBSD 4 months ago
COPYING Added GPLv3 license file. 6 years ago add pkg-config 6 days ago Fix wrong example path extension 1 year ago

Laminar CI status

Laminar ( 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.

On Debian Bullseye, this can be done with:

sudo apt install \
		 capnproto cmake g++ libboost-dev libcapnp-dev \
     libsqlite3-dev rapidjson-dev zlib1g-dev pkg-config

Then compile and install laminar with:

git clone
cd laminar
make -j "$(nproc)"
# Warning: the following will overwrite an existing /etc/laminar.conf
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.

Packaging for distributions

The pkg directory contains shell scripts which use docker to build native packages (deb,rpm) for common Linux distributions. Note that these are very simple packages which may not completely conform to the distribution's packaging guidelines, however they may serve as a starting point for creating an official package, or may be useful if the official package lags.


Issues and pull requests via GitHub are most welcome. All pull requests must adhere to the Developer Certificate of Origin.