Recorders built-in HTTP server listens on port 8083 per default. The nginx configuration, however, contained two location blocks that proxied to port 8085 instead, which prevented the website to render correctly.
- UPD: REC files now use tst from JSON payload as timestamp (#133)
- FIX: default file is /etc/default/ot-recorder
- FIX: add support for $OTR_BROWSERAPIKEY from environment (#156)
- UPD: packages now have API kill in them (#153)
note that messages which do not contain a tst (e.g CARD) will be stored with now (time(0))
the tst in the location message payload is also used for the REC filename
closes#133
- UPD: name on live map can be overriden by 'name' in JSON payload
- NEW: decrypted payloads have "_decrypted":true added to .rec file (#151)
- NEW: new configuration variable OTR_BROWSERAPIKEY (#146)
- FIX: Maps browser API key file (apikey.js) is now served by the Recorder (#146)
- FIX: add CFLAGS for base64 to conver Arch (#128)
- FIX: if defaults file can't be read, log an error (#131)
- NEW: otr_publish() from Lua reuses Recorder's authenticated, TLS-enabled MQTT connection (#140)
- UPD: changed systemd unit file (#137)
- UPD: README restructured (#138)
- NEW: ocat -v and api/0/version now show git version/commit
- FIX: Debian package dependency on libsodium13
This isn't really a great place for these, and they're not very complete
anyway. Better to put this in the proper docs, where it'll be obvious
and complete.
Add the standard OwnTracks MQTT topic as the first argument to
`ot-recorder` in the service file. This provides a usable experience out
of the box (otherwise the service file will fail with a help message).
If the user is on systemd it's reasonable to assume that they are also
using journald. This is the default on most (all?) systemd systems and
any admin who configures their system to send things to syslog instead
of journald can deal with one more thing that needs to be
changed.
Therefore, optimize for the majority and send logs to the default
journald. Additionally, don't send stdout to /dev/null because this
isn't the norm with systemd; stdout can provide valuable debugging
information; and journald provides facilities for filtering out stdout
in log output.
This isn't the normal way that systemd service files are written, and
lots of admins will probably be surprised to find that this is
happening. Therefore, remove it from the default configuration.
This is especially relevant given that the default ExecStart command
produces a help message, which causes systemd to mark the unit as
failed. This causes an infinite restart loop on default installs.
