http://coldfusion.com logo
Join Slack
Powered by
<@U06V253M4>, i'm working through a lucee 5 =&gt; ...
# lucee
j
@bdw429s, i'm working through a lucee 5 => 6 upgrade (on the non-commandbox official lucee image) and i'm having issues with the ortus redis extension.
Redis: No license activated. Enter a valid license key, or choose "trial".
i haven't started troubleshooting in earnest yet but thought i'd ask in case you knew what's wrong off the top of your head.
b
That's a good question. We haven't converted any of our sites to Lucee 6 yet (we've had a lot of issues just with our ColdBox tests passing on it). I'm not sure what may have changed there.
j
i'm thinking it has to do with the placement of the license file:
Copy code
secrets:
      - source: lucee_ortus_redis_extension_license_properties
        target: /opt/lucee/web/context/ortus/redis/license.properties
      ...
b
That would certainly make sense
prolly due to being a single context by default
Try putting it in the same location, but in the server context, if that's the context the extension is installed into
j
trying this:
Copy code
- source: lucee_ortus_redis_extension_license_properties
        target: /opt/lucee/server/lucee-server/context/ortus/redis/license.properties
another thing is i don't see the ortus redis (or whatever it is called) item in the admin's nav bar. i'd expect to see it there so i could, say, switch to trial mode, experimentally.
i wonder if that's a bug with the extension on lucee 6 (or if my expectation is wrong)
b
I'm not aware of Lucee changing how extensions add navigation items, but it's possible they changed something
The other option is that the extension isn't installed fully for some reason
j
didn't it only show up on the server admin panel before (the ortus extension nav item)?
(having trouble remembering when/where that appears)
i'm still getting that error, despite the new location,
b
it should have showed up in whatever context it was installed into
@jclausen may recall if we had the manifest for that extension to only allow a specific context or not
j
let me make sure it's all up to date (the extension, that is). i usually pin
ah, upgrade gets me at least partway there. i now see the "Ortus > Redis Cache". it didn't pick up my license but having that admin form let me change it to trial for now.
j
We haven’t certified any of our Lucee extensions yet on Lucee 6. I attempted, early on, but there were too many bugs with the early releases. I will try to circle back to that in the next few weeks. That said, I highly recommend configuring the license via the environment So much easier and less prone to error.
j
ah, didn't realize that was a thing, thanks. i'll switch to that.
in the meantime, this is where the extension wants the license in the official 6 image: 
/opt/lucee/server/lucee-server/context/context/ortus/redis/license.properties
i wouldn't have guessed 
.../context/context/...
but that's what it is.
j
Yeah, that one has bitten me a few times too. Hence adding the ENV support. 🙂
b
Yeah, there are "reasons" why Lucee has a double 
context
folder. They were so profound however, I forgot what they were, lol
Last I asked Micha, it was something about not having a better name at the time
j
naming stuff is hard. 🙂
s
it's why my son has the unique if also regrettable name of context-context
😆 3
2 Views
Open in Slack
PreviousNext
Powered by