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
CSRBot 59b8825b6e
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details
chore(deps): update dependency to v1.20.1
1 month ago
cli fix: golangci-lint and gosec warnings 2 years ago
pkg test(ci): start postgres db as drone service 1 year ago
systemd fix: systemd service unit 3 years ago
.dockerignore fix(Makefile, Dockerfile): optimization of the container image building process 3 years ago
.drone.yml chore(deps): update dependency to v1.20.1 1 month ago
.editorconfig fix: renamed project 4 years ago
.gitattributes fix: renamed project 4 years ago
.gitignore fix: Makefile 2 years ago
.golangci.yml fix: golangci-lint and gosec warnings 2 years ago
.markdownlint.yaml fix: add markdownlint config 1 year ago
Dockerfile fix: adapt go proxy settings 2 years ago
LICENSE fix(LICENSE): publish flucky under the apache 2.0 license 4 years ago
Makefile fix: Makefile 2 years ago fix: markdown capitalization error 1 year ago
docker-compose.yml chore(deps): update dependency postgres 5 months ago
go.mod chore(deps): update module to v1.14.16 5 months ago
go.sum chore(deps): update module to v1.14.16 5 months ago
main.go fix: golangci-lint and gosec warnings 2 years ago
renovate.json fix(renovate): init 1 year ago


Build Status Docker Pulls

flucky is a lightweight program written in go for reading data from sensors, for example with a banana or raspberry pi. In addition, flucky provides a REST-API to receive from other flucky installations measured values. All received measured values, no matter if they come directly from flucky or from a server instance of flucky with the provided REST-API, can be stored into a database.

Supported and planned sensors

Name Measured values Supported
BME280 humidity, pressure, temperature Yes
DHT11 temperature Yes
DHT22 temperature Yes
DS18B20 temperature Yes
SDS011 fine dust Planning

Supported and planned backends

Backend Supported
flucky WIP
Logfile CSV, JSON, XML
MySQL, MariaDB Planning
PostgreSQL Yes
SQLite Planning


flucky can be installed over multiple ways. For example over a specific linux distributions package or as container. The following table lists all repositories where flucky can be otained from, but flucky can already be compiled from source code.

Distribution Repo's
Arch Linux armv7, x86_64
Debian, Ubuntu, Linux Mint Currently not supported
RHEL, Fedora, Centos Planning
Container Image

Compiling the source code

An additional ways to install flucky is to compile the source code. There are two different ways to compile flucky from scratch. The easier ways is to use the pre-defined container image, which has included all dependencies to compile flucky. Alternatively, if all dependencies are met, flucky can also be compiled without the container image. Both variants are briefly described.

Compiling the source code via container image

To compile flucky via container image it's necessary, that a container runtime is installed. In the Makefile is predefined docker, but it's can be also used podman. Execute make container-run/flucky to start the compiling process.

$ make container-run/flucky
make container-run COMMAND=flucky
make[1]: Directory „/home/markus/workspace/flucky“ is entered
/usr/bin/docker run \
        --rm \
        --volume /home/markus/workspace/flucky:/workspace \
        volkerraschek/build-image:latest \
                make go-build \
                        VERSION=60ee044-git \
                        GOOS=linux \
go-bindata -pkg db -o ./pkg/db/bindataSQL.go ./pkg/db/sql/***
go-bindata -pkg goldenfiles -o ./test/goldenfiles/bindata.go ./test/goldenfiles/json/***
GOOS=linux \
GOARCH=amd64 \
        go build -ldflags "-X main.version=60ee044-git"
go: finding v1.0.3
go: finding v1.2.0

Compiling the source code without container image

Make sure you have installed go >= v1.12. Execute make flucky to compile flucky without a container-image. There should be a similar output as when compiling flucky via the container image.