Topics created by dmytro.hryn

@ilyavialkov I removed authentication through a file, but that didn't solve the problem:

caster: host: yccaster-svil.sigemi.cloud address: 0.0.0.0:2101 identifier: My caster operator: My organization nmea: 1 country: EST latitude: 59.44 longitude: 24.74 fallback_host: 0.0.0.0 fallback_port: 0 misc: Some notes configuration: auth: - type: http options: url: http://127.0.0.1:8888/yc-caster-api/mountpoints/ntrip_auth secret: super_secret api: host: yccaster-svil.sigemi.cloud address: 0.0.0.0:8080 api-keys: - "104ebb67-a4bq-4c20-we36-99cb759d1ee9" events: - type: file options: path: /var/caster/session.log types: - caster-ready - caster-terminate - connection-accepted - connection-terminated - ntrip-request-accepted - ntrip-request-rejected - ntrip-session-started - ntrip-session-ended license-key: ""

and now in the logs there is no attempt to connect the source, only this:

{"name":"caster-ready","timestamp":1689165626,"data":{"address":"[::]:2101","started_at":1689165626}}

@ilyavialkov Initially, I asked about authorization through a file, but now I realized that this is not my way. Authorization via http is more flexible and solves the problem when scaling casters with a single database. So I started developing the back-end. Thanks anyway!

@ilyavialkov i'm working on a project for a european company that makes robots that cut grass, initially we use caster BKG as a base but faced some problems with its operation and lack of necessary support. And now we are looking for an alternative, if everything suits us, we will buy a license and cooperate.