start
command will automatically have the JVM args added to it to load up FusionReactor.Open Fusion Reactor
that will do the same thing.upgrade --system
and you won't have to worry about suddenly getting a major FR upgrade one day that doesn't work with your license key.installID
setting can be any valid CommandBox endpoint installation ID, which means you can point to a custom HTTP URL, or ForgeBox slug, etc.conf/reactor.conf
inside of the FusionReactor home directory. If you want to script out settings such asreactor.conf
file that contains the settings you want the point this module at the file to be copied over when starting the server so FR will pick it up and use it. Just need in mind that this setting will override any manual setting changes you make in the FR web admin every time you start the server.reactor.conf
file somewhere for later useserver.json
to the new file. Remember, non-absolute paths are relative to the directory the server.json
lives in.reactor.conf
file may contain passwords or other sensitive information. It is in a java properties file format, so feel free to edit it and remove items you don't want. Also, take care when committing it to a source repo or making it web accessible so you don't reveal information. There is currently no support for environment variable expansions in this file, but perhaps we'll add it if it's useful.server.json
to control these dynamically on a per-server basis!fradminpassword
frregisterwith
frshutdownaction
frregisterhostname
frregistergroup
frlicenseservice.deactivateOnShutdown
frlicenseservice.leasetime.hint
fr.cloud.group
fr.request.obfuscate.parameters
fr.application.auto_naming
fr.application.name
/fusionreactor/
to CommandBox as well or this feature will not work and you'll just get an Nginx/etc 404 instead.