Does JEC support lazy loading of config?

[Jared Schmitt]

I've installed JEC locally via Docker (see docs) and it's working. Much easier than anticipated to be honest - well done Atlassian! 

As it seems, we need to define each available action in the main config file.

After my initial test I've added a second action to it and the script associated with this new action is also present in the container. However when calling the new action from JSM, it's not working, stating 

No mapped action is configured for requested action[fancy-script]. The request will be ignored.

Which leads me to assume the updated config file didn't get read by the JEC process and hence it doesn't know about the new action.

Q1: Is JEC supporting lazy loading of config files?

Q2: If not, how can we trigger a config reload within Docker? (no systemctl available)