Reload configuration from file

Hello.
Is there any method for reload rules configuration from file without full restart?
Signal for process or API call?
kill -HUP only reopen log files.

Hello,

If you change config manually, you need to re-start Nimble manually each time. This is done on purposes so that WMSPanel UI settings would always have priority.

As for logs, you may set their rotation as described in config file specification: http://blog.wmspanel.com/p/nimble-streamer-configuration.html

Any update on this?
I'm trying to see if nimble streaming can be a wowza replacement in my infrastructure (all private with no internet access).

How to reload the server without taking down everything?
Any API to do that?

You still need to restart Nimble to apply config files change, there is no API for reload config.

So, no way to achieve stability with Nimble Streamer.
It will break everything on each reload.

Thanks.

You can use WMSPanel to apply settings without the re-start.

Unfortunally this will not work in our infrastructure.
We need a deep integration and control with tools that we use.

WMSPanel will not work at least for these:
- single point of failure (if you go down, we cannot update servers regardless your setup)
- apicalls per day limitation (too restrictive and unnecessary when we could call the server directly)
- high risk of configuration loss / misconfiguration by an attacker that attacks your systems, or somebody in your company that want to do that against you

I'm sure that there are other reasons why prevent any cloud management for critical systems.

Do you have a WMSPanel to install on-premises?

The Nimble/WMSPanel interaction is designed in a way that if the panel is unavailable, Nimble Streamer will still work with no interruptions.

We have 15K requests per day limit which is more than enough for any of our customers.

And if you are worried about loosing configuration, you can back up nimble.conf and rules.conf in order to restore any time later.

Our panel is not available on-premise, SaaS is the only option.

Point 1: Nimble will work but not the changes made through API, because the API will be down, so no way to obtain a stable integration.

Point 2: Yes, not for us. Need one call per stream every 3 seconds

Point 3: I can backup everything but an attack to your systems can create downtime to my customers. Backup up and restore is not enough.

It's ok our server cannot fit everybody's needs.