Thanks.
I've added an @ask-update to PLIST so the update from older versions
won't happen automatically, giving users a quick heads-up, but I think
we need something (probably in pkg-readme) showing what people need
to do. As they're local changes in the port there's no relevant upstream
doc that we can defer to.
(I hate java stuff for this, if it was C I'd suggest just patching the
source, but that's going to be a lot more of a pain here ;)
On 2024/07/31 15:24, Renaud Allard wrote:
> Just for info, I have received the confirmation that setting
> server.statistics to an empty field disables the analytics.
>
> On 7/31/24 8:18 AM, Renaud Allard wrote:
> >
> >
> > On 7/31/24 12:26 AM, Stuart Henderson wrote:
> > > On 2024/07/30 15:43, Stuart Henderson wrote:
> > > > I want to check this on my installation first - please ping me if I
> > > > haven't committed or replied within a few days.
> > > >
> > > > > The default.xml configuration file is now obsolete, although
> > > > > it will still
> > > > > work if you have it defined in your traccar.xml.
> > >
> > > ..so this got committed already - but there are problems, and now that
> > > it's been committed we can't really revert it because people might run
> > > it and trigger schema changes running which may make it hard to go back.
> > >
> > > - Users who have touched traccar.xml will need to merge in the things
> > > you've now added in the patch (i.e. the log path, and only listening
> > > to localhost) because there's no automatic way to do that.
> > >
> > > - The package no longer includes default.xml, so an existing <entry
> > > key='config.default'>/usr/local/share/traccar/conf/default.xml</entry>
> > > is not valid.
> >
> > I don't think there is an easy way which would work for everyone around
> > merging the changes manually unfortunately. But this happens for major
> > updates of postgres too for example.
> >
> > >
> > > - Did you find the traccar.xml alternative to removing server.statistics
> > > from the default config? I guess setting to an empty string _might_ work
> > > but not tested yet (I need to setup a test instance again to try this -
> > > at the moment I only have my main work one running).
> >
> > This is not exactly clear, one page suggests removing it from the
> > default config (but that doesn't exist anymore) and the other page tells
> > that there is a default value.
> > I am using <entry key='server.statistics'>""</entry>
> > But I have now asked the question and will come back with the answer.
> >
> >
> > >
> > > (This is all exactly why I did not commit either of these updates yet.)
> > >
> >
> > I also forgot to tell that you now need an API key if you want to use
> > google maps (6.3 change).
No comments:
Post a Comment