[Commandbox 6] FusionReactor 2025 Question

Communities CommandBox CLI
1

I love the FusionReactor integration with Commandbox servers. It’s a huge help when developing apps. However, I met with David T at FusionReactor this morning and noticed that the Commandbox version of FR is 12.1.1, but the most current version is 2025.1.0.

I tried following the doc instructions and re-ran install commandbox-fusionreactor, but it seems to be stuck on version 12.

Is there a way to bump it to the next major version?

1 Like
2

Are you using an env file with your CommandBox server? If so, you can specify the version there.

BOX_SERVER_FUSIONREACTOR_INSTALLID=fusionreactor@2025.1.0

3

I’m waiting for someone to test it and send me a pull request to the module to update it. You’re about the 4th person to ask, but still no pull has been sent :slight_smile:

5

Tested (probably unorthodox) but here’s what I did:

  • Deleted the fusionreactor folder in my test app
  • Deleted the commandbox-fusionreactor module and artifacts in Commandbox
  • Forked commandbox-fusionreactor and updated installId.
  • install github:homestar9/commandbox-fusionreactor#patch-1
  • Exited out of all instances of Commandbox.
  • server start on my test app

Wohoo! Version 2025.1.0 and I tested request history, JDBC history, and all looks good to my eyes.

image

Submitting the PR now for review and approval.

6

You didn’t need to go through all that effort just to test it. You can set the installID right inside your server.json

server set fusionreactor.installID=fusionreator@^2025

I commented on your pull.

7

Fixed. Sorry about the error.

@bdw429s there’s the right way, and the Dave way. LOL. Thank you for the tip. I’ll remember that next time.

1 Like
8

No worries-- and for the record, the reason I set up the module to automatically grab new minor or patch versions of FR, but NOT to automatically grab new major versions is because major versions (per semantic version) rules can introduce breaking changes into a library. For a user with a given version of the CommandBox module installed, I don’t want them to restart their server one day and suddenly it’s broken in prod because FR rolled out a new major version overnight with breaking changes. FR tends to be pretty backwards compat, but I want to be safe. When a new major version of FR comes out, I’ll let people test it a bit before updating the module to use it, and I always do a major bump of the module version as well. So if you have an older version of the module, you’ll need to force the major update to “opt into” the new major version update of FusionReactor.

1 Like