@bdw429s (or anybody else), it's not clear whether there's a fee associated with using the ortus redis extension. could you explain? in the lucee admin, it's seems pretty clear that it's free, what with the word "free" being right there in the title: "Ortus Redis Cache Free" but in the lucee admin, there appears an "ortus -> redis cache" menu item with a license box, and the ortus site has fee info: https://www.ortussolutions.com/products/redis-lucee i'm striking out with the old third party extension i'd been using (not compatible with new lucee version) and the LAS version seems broken.

The word "free" comes from Lucee. Way back in the day, Railo was going to have a store to facilitate selling paid extensions, so the extension provider was coded to have a price. The store never materialized, so if you want to sell an extension, you just have to handle the licensing on your own inside the admin. So you can install our ext for "free" (because there's no other option) and use a 2 week trial, but the you will need ti activate it. Check out our product page where all the pricing is explained. The Lucee admin doesn't really give us much control over showing the purchase options

thanks, @bdw429s. sounds like a lucee enhancement request is needed. it makes it seem like ortus is doing a bait and switch, even though it's not the vendor's fault.

Yeah, perhaps we can update the description if it to help better explain.

@bdw429s how does one automate the post-install license piece? we're containerized so i know how to install the extension and how to configure caches, but i don't see docs on how to do this part via CaC:

If you purchase the container license, we'll send you a special activation key to use

what about for the two-week trial, tho. can you just go forward without this step? we want to make sure this solves our issue first.

What is "CaC" in this context?

configuration as code. i can't have manual steps.

Yes, that's the process, but your manually created license key will only with on the server it's created on. That's where you can contact us to give you a multi-server activation code for your container license

okay, i'm not clear on how to do a manually created license key, but i've reached out to support for a trial key.

You don't need a key for trial.

I'd like to automate the trial license installation. I might be able to make it work manually in the meantime but it would be tough to keep track of doing it every time a container is created. The problem is that the issue we're dealing with might take a few days to prove out since it doesn't have a good repro case. I think your and my wires might be crossed a bit because my idea of a trial license might be different from how the extension does it. I would want, say, a cross-instance license key that stops working after x days but it seems like this trial implementation isn't quite like that, so it makes it weird to use with short-lived containers. (Unless I'm misunderstanding something.)

Our trial doesn't have a license key at all. You just select "trial", and then it's fully functional until the timer runs out.

Yup, that's what I'm coming to realize, thanks.