New ForgeBox Features — March 2018
ForgeBox 3.0.0 has landed with tons of new features and updates including ForgeBox Storage and ForgeBox Lucee Provider!
Tweet
ForgeBox 3.0.0 has landed with tons of new features and updates including ForgeBox Storage and ForgeBox Lucee Provider!
We are very excited to bring you a new commercial product release for the Ortus Family: Redis Lucee Extension The Redis Lucee Extension allows you to natively connect to a Redis Server cluster and leverage it for distributed caching, session/client storage and distribution, cluster RAM file systems, and much more. It can allow your Lucee servers to scale and extend easily by leveraging Redis Server as the platform of choice for session/cluster managements, caching and virtual file-systems.
If you have ever asked yourself these questions, then our Lucee Extension can help you:
We have been working with Redis Server for many years and it has been a true pleasure to not only build scalable farms with it, but also it is incredibly responsive when it comes down to key-value storage and caching transactions.
Here are some of the major features of our Redis Extension:
cachePut(), cacheGet(), <cfcache action="get|put">
ram://...
<cfquery cachedwithin>
<cffunction cachedwithin>
<cfcache action="content|cache|serverCache">
Please visit our Extension page for all the necessary resources.
Today we released our 3.8 series of docker images ( current source version 2.1.0
) which include a number of improvements and enhancements.
Change Log
On the heels of and in conjunction with the 3.7.0 release of ContentBox, we are pleased to announce the 3.7.0 release of CommandBox ( a happy coincidence that the version numbers of the two are the same! ).
This release provides major updates in security and functionality to the CFConfig module, which may be used to configure CFML servers at runtime. The settings and environment variables, which were previously handled by the bash script used to start the image, are now delegated to CFConfig. You can read more on using environment variables for CFConfig here.
We've been using our CommandBox Docker images for awhile now for multi-tier development and deployment. We've also received a lot of great feedback from the community that has helped to expand the power and flexibility of the those images in orchestrating CFML server environments.
One important aspect of non-development deployments of applications on the CommandBox image, is the need to warm up the server by seeding the CFML engine file system and configuration before the application is deployed in its target environment/tier. Other than the default Lucee 4.5 engine, which is what CommandBox, itself, runs on, any CFML engine specified in your application's server.json
file is downloaded upon server start. Depending on the latency of your Docker environment's connection, this can mean that a bare-bones first run of your application can take minutes to start up, rather than seconds. For obvious reasons, this is not desirable.