When running Siegfried as a long-standing service, for example as a docker service, it would be important to keep Siegfried up-to-date with the signature database. But, currently, there is no way to call the update action via the service, nor to somehow schedule an auto-update.
This could be done in one of the following ways:
- Add a new action to the Siegfried server API, e.g.
GET /update, which would call the update action. An external service could be setup to call this endpoint periodically
- Including an auto-update feature into the tool, specifically when it runs in server mode, e.g.
sf -serve localhost:5138 -autoupdate 24h
When running Siegfried as a long-standing service, for example as a docker service, it would be important to keep Siegfried up-to-date with the signature database. But, currently, there is no way to call the update action via the service, nor to somehow schedule an auto-update.
This could be done in one of the following ways:
GET /update, which would call the update action. An external service could be setup to call this endpoint periodicallysf -serve localhost:5138 -autoupdate 24h