Can I restart the application from within a plug-in?

[richardeakin]

I've got a python script that I want to run before our application starts up in the morning that downloads and caches new content from our CMS. I'm thinking that the easiest way to reload after this happens is to restart the application. Is there a way to send a command to AMPM to do this? I realize I could call App::quit() from within C++ and rely on the heartbeat checker to cause a restart, but this feels a bit hacky.

Side question: how would you recommend running the python script? It doesn't look like a can run a "preLaunchCommand", although I think I can get by with a "postLaunchCommand", letting the app run in the meantime, then restarting afterwards.

Thanks for any help.. and really enjoying using this tool that you've created.

[LRitesh]

Josh might have a better answer once he's back from vacation, but one way to relaunch your app would be to save a new version of "ampm-restart.json" after loading new content. Ampm will constantly watch this file for changes, and will relaunch the app whenever it saves.

[endquote]

We have a very similar situation on a current project. We have a node script which will download content from a CMS on some schedule. The app should restart when that's done, but the downloader tool doesn't really talk to ampm or the app.

Most likely we'll have the downloader run at some specific time and use the ampm restartSchedule feature to restart the app at some time after that, when we're reasonably sure the first tool has completed.

But: adding some feature by which an app could request its own restart isn't a bad idea. And Ritesh's suggestion would be a current way to do it without ampm code changes.

[endquote]

Actually, a plugin can $$persistence.restartApp().

I'm adding a documented restart feature anyway, though.

[richardeakin]

(..back from vacation..)

Just wanted to mention that @endquote we ended up doing the same thing you are doing - we refresh content first thing in the morning, then run AMPM once that process is finished. Simple solution, drawback being that we couldn't (easily) update the content while the app is running, but not the end of the world.

Probably next project I'll look to see how I can make the app triger a $persistence.restartApp(), as that seems like a pretty clean solution to me.