Tweet
Luis Majano
Patrick is the director of Paper Oh and discusses his experience of ColdBox training during CFSummit 2016 and his plans to implement ColdBox and ColdFusion in their applications in Brazil.
Luis Majano
Today we are very excited to bring you ContentBox version 3.6.0. This release was all about improvements to the core, localization and internationalization for sites, many bug fixes, UI improvements and updates to our containerization strategy. Please see below the major areas of improvement and our full release notes.
The installer module is now available as a standalone module using the slug contentbox-installer-module. This will improve our container and your container strategy as now you can bring in the installer on demand via CommandBox.
install contentbox-installer-module
Thanks to the Computer Know How guys you can contribute your own CSS files to the CKEditor instance so the content has your theme's look and feel. Please note, this is mostly usable for theme developers and module developers.
The event is called cbadmin_ckeditorContentsCss and it will receive a struct with one key called contentsCss which is an array. You can then append CSS style sheets to that array that CKEditor will showcase.
function cbadmin_ckeditorContentsCss( event, interceptData ){
// Add css
interceptData.contentsCss.append( "/path/theme.css" );
}
Thanks to the Computer Know How guys, this release sports many i18n improvements.
A ContentBox application depends on the ColdBox i18n module which gives you the ability to serve any content in any language, use resource bundles and use the resource utilities. However, we have now exposed the ability natively for users to change locales via the UI module using our URL of: http://site.com/__changelang/en_US. The route expects an ISO valid language code in the format of code_variant.
Note By default, visitor locale's are stored in the
cookiescope. You can change this via theconfig/Coldbox.cfcconfiguration CFC.
The CBHelper object can now produce these links for you in your layouts, themes and views by leveraging the following method:
/**
* Link to the __changeLang route, this is where the fwLocale is changed
* @lang The iso language code
*/
function linkLanguageChange( string lang = "en_US" ) {
return getRequestContext().buildLink( '__changeLang/' & arguments.lang );
}
All caching strategies have now been updated to allow for locale to determine its key. This way, every visitor's language will be cacheable and performant.
Luis Majano
Tim Cunningham is the Vice President of Primoris Services. He discusses how they leveraged ContentBox Modular CMS to deliver a payment portal for their API payment services.
Luis Majano
Bill Reese from crosstrackr discusses how he leverages CommandBox/ColdBox and the Box eco-system for building their ColdFusion (CFML) applications.
Luis Majano
Ohh happy day, today we get a minor release in ForgeBox.io and our first blog post announcement about ForgeBox releases. As the product matures and we continue to pipe in new functionality, be expectant of blog posts relating the new functionality in ForgeBox. Most of the issues in this release are cosmetic and improving existing functionality. Enjoy!
Luis Majano
We are very excited that the Portainer.io crew has added support for CommandBox and CommandBox docker image deployment. If you have not heard of Portainer, then let's start there first.
Portainer is an open-source lightweight management UI for easily managing your docker host or a swarm cluster. It is available as a docker image or a standalone binary for any operating system. I was quite impressed with all the functionality out of the box with portainer, and the ease of use of the interface. It really made, for me, put all the questions I had about docker to rest thanks to finally visualizing them. I also found useful their live demo, which is great as well and got my appettite ready for delving into it.
To do a quick start for portainer just use the following commands:
docker run -d -p 9000:9000 \ -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
This will run the docker container for portainer on port 9000 and it will manage the local Docker engine.
Portainer has the concept of quick application templates for easily deploying applications and trying them out. From here you can navigate their great collection and you will find our two docker images: CommandBox and ContentBox. We will use them to launch CFML applications with CommandBox or a full fledge CMS instance using ContentBox CMS. Below are the screenshots for each template so you can get started with ColdFusion (CFML) and ContentBox CMS with docker:
Using the CommandBox template you can fill out the following information:
You can run the template as is and it will generate the sample ColdFusion page which is not very fancy. So we would encourage you to point it to a ColdFusion application so you can see your application being dockerized!
Using the ContentBox CMS template you can fill out the following information:
You can run the template as is and it will generate a new ContentBox CMS site with its very own in-memory H2 database and clustering capabilities. However, you will need to follow the installer and then remove it via environment variables so it does not recreate the image on each startup. Please refer to our docker image documentation for further information.
In coming tutorials we will be demonstrating how to use Portainer to leverage a docker swarm with our images. From service creations, to on-the-fly modifications and much more. So stay tuned!
Luis Majano
Brian Sappery, Applications Architect for shop.com, discusses how they leverage the ColdBox Platform and ColdFusion for delivering a high impact and mission critical RESTFul applications, that powers much of their multi-million dollar infrastructure.
Luis Majano
The CTO for pipelinesuite discusses how they leverage the ColdBox Platform for delivering a high impact Software as a Service built in ColdFusion (CFML).
Brad Wood
There is a new command in town in the CommandBox 3.7 snapshot build. If you want to get the current snapshot build of CommandBox 3.7 to try this out, and play with it, simply run the following command and it will direct you to the latest bleeding edge download page:
CommandBox> upgrade --latest
This command is called testbox watch and it is similar to testbox run which can be used to run your projects unit or integration tests. The difference is that testbox run will run your tests a single time right then, whereas the testbox watch command will stay running until you stop it with Ctrl+C. The command will watch the files in your project for changes, and every time you save a CFC file, it will run your tests immediately, outputting the results to the console window. This gives you instant feedback as you develop as to whether you just broke something.
CommandBox> testbox watch
Watching Files...
Executing tests via http://127.0.0.1:59060/tests/runner.cfm?&recurse=true&reporter=json, please wait...
TestBox v2.5.0-snapshot
---------------------------------------------------------------------------------
| Passed | Failed | Errored | Skipped | Time | Bundles | Suites | Specs |
---------------------------------------------------------------------------------
| 16 | 0 | 0 | 0 | 132 ms | 2 | 4 | 16 |
---------------------------------------------------------------------------------
Stopping...
CommandBox>
If you want to see a demo of this in action, check out this screencast I made.
CommandBox> testbox watch help
You will see that there are a handful of way to configure how it runs. The watcher itself can be controlled by setting up the parameters you want in your box.json file for the project. Here's a rundown of the configuration elements you can set. All of these are optional except the testbox.runner.
CommandBox> package set testbox.runner=http://localhost:8080/tests/runner.cfm
CommandBox> package set testbox.verbose=false
CommandBox> package set testbox.labels=foo
CommandBox> package set testbox.testSuites=bar
CommandBox> package set testbox.watchDelay=1000
CommandBox> package set testbox.watchPaths=/models/**.cfc
box.json fileSo your box.json file may look something like this once you've set it up.
{
"testbox":{
"runner":"http://localhost:8080/tests/runner.cfm",
"labels":"foo",
"bundles":"test.specs",
"testSuites":"bar",
"verbose":"false",
"watchDelay":"1000",
"watchPaths":"/models/**.cfc"
}
}
Luis Majano
If you will be attending this year's CF.Objective (Which you should!) on July, then you can attend our ColdFusion CommandBox training (July 18-19) and get a whooping 25%! You can use the discount code cfobjective and be on your way to learn how to evolve your legacy ColdFusion applications by using modern tooling like CommandBox!
You can also follow this link: https://dc2017-commandbox.eventbrite.com?discount=cfobjective to purchase your registration.
In this training we will review the ins and outs of CommandBox so you can incorporate it as your ColdFusion companion tool. From CLI and operating system integration to ColdFusion engine management and portability with Docker and container strategies. This training series will be led by CommandBox creators Brad Wood and Luis Majano. Whether you are a ColdFusion expert or novice, this bootcamp will challenge you and refresh your skills to be able to modernize your ColdFusion (CFML) applications and servers.