ztmr

Results 23 comments of ztmr

What if we change ErlyDTL so that it will be possible to append some kind of metadata to each of the tag/filter modules? CB would add something like {cb_parent_application, framework}...

I guess you have to change this file: priv/initdb so that there are spaces in between command and flags, so: "A-N" needs to be "A -N" We haven't updated this...

A number of thoughts on this topic... This is my initial steps (roughly): - `rw` - ask for non-root username to be created and create it - put this user...

I was looking for the same (auth against KeyCloak and GitLab) and ended up doing this: https://gitlab.com/ztmr/traefik-forward-auth/commit/1131d6b2bfd127a0084459a937d6c20b5844afcc ...this is tested with Google and GitLab (self hosted) but should work with...

The master does not build at all because of the frequency datatype mismatch. I've quickly hacked it [here](https://github.com/flightaware/dump1090/commit/d6679fcc424aa8c4b7d4ed92680b070ea99e22b2) but this PR seems to be much more sophisticated approach so I...

This is the OS version where I was building from scratch (everything including bladeRF): ``` $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04...

OK, I see. There are two precompiled packages, one for 1.x and another for 2.x. What about something like [this](https://github.com/flightaware/dump1090/compare/master...ztmr:master) then? It seems to work well: https://gitlab.com/ztmr/dump1090/pipelines/57288072

OK, I have misunderstood -- they say the frequency internal data type has changed since 2.x.x but the abstract type has first appeared at 1.9.x. So the current code works...

So just git-blamed the header and it looks like the type has appeared in 1.9.2 for the first time. But according to tags, 1.9.2 was not released and since the...

Yup I was thinking of polyfill for exactly the same reason (not having ifdefs all over) but came to conclusion that for just one occurence, it would be more confusing...