8 Commits

Author SHA1 Message Date
Jan-Piet Mens
fde6940993 ensure docker entrypoint uses $OTR_TOPICS if defined, with fallback to $OTR_TOPIC
addresses #86
2024-10-30 12:49:01 +01:00
Maxim Baz
3201dfacd6 Allow passing CLI args to recorder 2024-08-01 01:13:28 +02:00
Steffen Vogel
59db28f3c9 re-add entrypoint.sh 2022-05-16 10:05:35 +02:00
Steffen Vogel
86627d5237 remove entrypoint script 2022-05-14 10:16:14 +02:00
Toon Schoenmakers
9661dff4e8 Updated entrypoint.sh to not forget arguments
When running as root this script would get executed as the appuser, but the possible arguments would be forgotten.
2020-08-12 15:30:36 +00:00
Marco Paganini
47e273651c Run ot-recorder as an unprivileged user.
- Default UID is 9999 (defined with EUID=9999) inside Dockerfile.
- Please note that the docker volume is visible as a directory on the
  host under /var/lib/docker/volumes.  This is normally not a problem,
  as this directory is not accessible by regular users on the host.
- It is still possible to redefine the UID by passing -e EUID=<uid> to
  docker run, but that should not be necessary in most situations.
  This fact has been left out of the documentation as it only appeals
  to more advanced users (who will look at the Dockerfile directly.)
2020-03-12 22:10:37 -07:00
Toon Schoenmakers
8b1409608f Update entrypoint to allow passing arguments to ot-recorder 2019-03-06 14:32:58 +01:00
Malte Deiseroth
8b63ac0296 New Dockerfile for Recorder
The problem with the current solution is that it provide a monolytic
multiprogramm docker container. However the idiom of docker is to
have one service per docker container. If multiple services are
needed multiple docker container should be used. Docker-compose
makes this easily possible.

Another isse is that the container automatically creates certificates
and sets up encryption using a script. Also this violates docker
idioms, because certificate handling can be done using specific
containers like letsencrypt. It further makes it hard to include this
image into an existing and possible complex infastructure.

A further goal of mine would be to generate a Hassio addon for the
homeassistant project from this. The current dockerfile makes this
kind of hard.

What I did:
- Slimmed down the container to about 10MB by using alpine as a base
- Added a `docker-compose.yml` file that shows how to build and run
  the container
- Added a `docker-compose-mqtt.yml` file to show how a mqtt broker
  can be added. This shows how a plug and play solution using
  docker could look like.
- Changed the docker image label to owntracks/recorder
- Added documentation on how to use and configure the image
- Simple travis file for possible automatic building in the near
  future
- Removed automatic certificate handling
  Instead provide `config` volume to allow configuration.
- Removed arm32v7 build
  should be readded later but I dont have a setup for testing right
  now

What might be added at some point:
- Example with nginx reverse proxy
- Example with letsencrypt certificate
  This could also be an example for a complete plug and play
  solution. Proxy, SSl, MQTT and Recorder.
- Default resolv.conf file with all default options and documentation
- Upload to docker hub
- Change name to owntracks/recorder
- Some more examples for eclipse mosquitto
2019-01-08 16:55:16 +01:00