cfml

Is there are tool for exporting FusionReactor configs? I know you can copy the reactor.conf, but that doesn't handle all the plugin configurations. If I just parse the cmconfig/com/intergral/fusionreactor/plugin/ folder for files that end in .conf and migrate them to a new install, would that suffice?

<@U0AEFTKRV> No, there's nothing I know of

Moving the conf files to a new install should do what you need

I wasn't sure if there were other metadata files (like maybe some *.properties files) or anything else that should be preserved as well.

It sucks that they just dont store all the configurations in reactor.conf or at least put them all in the ./conf/ folder so they're in a single place.

It would also be really nice if they had a comprehensive set of env vars that could be used to control all settings like Elastic's APM has

Maybe ask on the fusion-reactor channel, see if the horse's mouth has any ideas.

<@U0R6WFD7S> This is the fusionreactor channel :slightly_smiling_face:

They don't tend to chime in unless you tag them.

I just went through this recently with a bunch of servers. Copying the config file(s?) over saved me a lot of manual configuration (pretty sure it was Brad who told me about the config files at the time). 

I just had to change server or instance specific things but that was only one or two places (i.e. the from address on alerts is unique per server for me). It saved soooo much time though

I was on the hunt for pretty much the same thing… a way to export and import or use env vars but export/import didn’t exist and, while I seem to recall there being some env vars available, there weren’t enough to make them useful 

Generally speaking, only the debugger and profiler store their config in the cmconfig directory, most settings are contained in the reactor.conf.

If you need to take the settings in cmconfig, you can just clone the entire cmconfig directory so there is no need to export and reimport it.

We are aware that the config for FusionReactor requires some optimization and this is something we plan to do going forward, currently, however we have other required changes so have not been able to work on it yet.

<@U3AJE1R28> has been working with me via email on this. I know the Daily Report configuration is stored in the cmconfig folder as well, so what I ended up doing is creating a couple of shell script that backs up the conf/ and cmconfig/ folder. It archives them into a .tar.gz file.

Then I have an import shell script that reads .tar.gz file and exports any files which have a matching parent folder (although you can force it to just extract everything). I did it this way because I'm actually get ready to migrate from ACF to Lucee, and there's at least one plugin that's different and I wanted to avoid carrying over any folders that were not needed.

In my local testing, it seems to be working great. Getting ready to test it w/our new production environment.