Multiple front ends (due to customisation)
Why do you need to disable caching if there is still single back-end?
As the updating of the device occurs every 5 mins or so when there is multiple front ends (on the duplicate front ends) whereas on the main front end it is fully live.
Is there a way to even shorten the cache time a bit?
I'm still confused about the question. Are you sure you mean front-end and not back-end?
Hey Anton
yes this is correct.
the layout is:
MYSQL database (replicated to run advanced reports and not cause load on the main system)
Customised Traccar interface (for internal usage, to run said advanced reports)
Traccar front end (hooking to the same DB as the customised traccar, for user facing actions)
the customised traccar updates as soon as the packet comes in
the stock traccar front end has about a 5 min refresh time on positions (if you reload)
How many Traccar back-ends do you have? Front-end doesn't talk directly to the database. There must be a back-end.
When I say "Front end" I mean the full traccar install, not just the front.
So, when you says "front end" you don't actually mean front end? I don't think there is any easy way to run two instances of Traccar in parallel. Some data is only available in cache; it's never read from database (e.g. current positions).
Thanks Anton.
Hi Anton
When running multiple front ends, how do you disable the apparent caching that occurs within the application with multiple front ends hooking to the same back end DB?
All data coming to one location, but different client access on the front ends (not sure where the position cache/refresh rate is set)
Cheers
Cam