mockoon-cli live update

[AKABTB]

When I am updating the data file, I want mockoon-cli to sense the changes in real time, without restarting the service, like client software does.

[255kb]

Thank you for opening the issue @AKABTB. I would kindly ask you to follow the issue template next time.

[theo-staizen]

I would also like this feature, if possible. Perhaps through a --watch flag?

[benlei-gfm]

I'm trying to compare mock-server and mockoon, and it seems like mock-server has this feature built in.

Would be great to have this also in mockoon to make it a stronger choice.

I've also noticed that the UI doesn't watch the settings file. As such if I were to make modifications to a route directly on the file, the Mockoon UI wouldn't be aware of it. Then if I do make a modification with the Mockoon UI, it overwrites/loses my manual change.

[255kb]

@benlei-gfm

I've also noticed that the UI doesn't watch the settings file. As such if I were to make modifications to a route directly on the file, the Mockoon UI wouldn't be aware of it. Then if I do make a modification with the Mockoon UI, it overwrites/loses my manual change.

This has been added in v1.19.0. You must enable it in the settings.

[benlei-gfm]

I actually just found that out - kind of weird that it's disabled by default though...

[vltansky]

Where can i find this settings? @benlei-gfm @255kb

[255kb]

Where can i find this settings? @benlei-gfm @255kb

@vltansky This setting is only for the UI (ctrl+, or top menu, Application -> settings). The CLI currently offers no monitoring.

[avrezvanov]

I want this opportunity too. Automatic restart of the CLI.

[wilcorrea]

Hey guys. Do you have plans to "live update" feature? Can we help on it?

[255kb]

Hey guys. Do you have plans to "live update" feature? Can we help on it?

Sure, any help is welcomed. Let me know if you want to work on it, we can discuss the implementation as there are multiple use cases to cover:

• running the CLI with --daemon-off (foreground process)
• running the CLI without --daemon-off (PM2 managed process). Can we monitor correctly? Not sure.
• running the CLI within Docker:
  • with the provided Docker image, data file is passed at runtime.
  • with a custom Docker image, data file copied inside the container (maybe easier).

And for all theses cases, a path to a local data file can be passed as a param, or a URL. Do we monitor URLs by using some polling? Or do we exclude them from the feature?