The Ortus BlogBox

"Ortus: A rise, beginning, coming into being, born, the origin!"

 

 

Category Filtering: 'commandbox'

 

Screencast showing how to start Adobe, Railo, and Lucee 5 servers in CommandBox

Brad Wood
May 16, 2016

 

We recently announced the availability of CommandBox 3.1.0 beta for testing.  We've also prepared this short screencast that shows starting up Adobe, Railo, and Lucee 5 servers in CommandBox.

If you'd like to see more, please check out our official announcement blog that overviews all of the CommandBox 3.1.0 beta features.

https://www.ortussolutions.com/blog/commandbox-v310-beta-ready-for-testing

CommandBox, Tutorials, Tutorials 3

ContentBox 3 - Extending ContentBox 3 easily with Modules

Gavin Pickin
May 16, 2016

 

I can see the light at the end of the tunnel. ContentBox 3.0 has been a massive project, with so many changes and features, its really exciting to be a part of it. The good news, the testing is almost all done, we're going to cut a final release very soon. This means I have a lot of great things to blog about, and if you want a front seat to a full tour, you need to make sure you are coming to Into The Box (Ortus Solution's very own 1 day 2 track conference), June 14, 2016, in Minneapolis University of St Thomas, MN. USA - the day before Dev.Objective().

Note: You should attend both of these Conference, they are great, and the Ortus Solutions and ColdBox team will be giving several presentations at Into The Box and Dev.Objective()). They are great learning & networking events, hope to see you all there.

CommandBox, Conferences, ContentBox CMS, ForgeBox 0

CommandBox v3.1.0 Beta Ready For Testing

Brad Wood
May 05, 2016

 

We are excited to announce availability of CommandBox v3.1.0 Beta for testing and feedback.  Our goal is to have this released in time for Into The Box so that means we need you to help get it stable and ready to go.  There are a collection of bug fixes, and several very nice improvements, the biggest of which is the ability to start up any CFML engine you want on demand including Lucee 5, Adobe ColdFusion 2016 and Railo.

How do I get it?

First things first.  If you already have an older version of CommandBox installed, you can run this command which will give you the URL 

CommandBox> upgrade --latest

Or just hop over to our integration server and grab the correct binary for your OS:
http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/3.1.0/

We're still working on the GitBook docs for this release, but you can use the "help" commands to get additional info.

What do I need to know?

The first thing to take note of is that the beta of CommandBox is currently pointing to our stage server since we are using a brand new ForgeBox API.  This will be fine for testing, and even installing most packages, but it's not guaranteed to be the exact same packages as what's on production.  

If you want more juicy details on the new features of 3.1.0, please check out these two blog entries on my personal blog:

Exciting New Features In The CommandBox 3.1.0 Bleeding Edge

CommandBox Multi-Server Support Now In Beta (v3.1.0)

Also, a full list of tickets completed thus far are available here in JIRA:

JIRA Search for "Resolved" tickets in the "3.1.0" release.

What's new?

Here's an overview of the big changes and improvements in this release.  There will be more to come, but this is what we have done so far.

Multi-Server Support

The CommandBox CLI runs on Lucee Server, and the web servers you could start in any directory used to only be Lucee too.  Now you can start up a web server of any kind and version.  Currently supported CF engines are:

  • Adobe ColdFusion 2016.0.0+297996
  • Adobe ColdFusion 11.0.0+289974
  • Adobe ColdFusion 10.0.12+286680
  • Adobe ColdFusion 9.0.2+282541
  • Lucee Server 4.5.2.018 (embedded, so no download needed)
  • Lucee Server 5.0.0-SNAPSHOT+243
  • Railo Server 4.2.1+008

Starting up a CF server is still super easy.  Everything you need will be downloaded the first time you start the server and cached for subsequent restarts.  

# Start the default engine
CommandBox> start

# Start the latest stable Railo engine
CommandBox> start cfengine=railo

# Start a specific engine and version
CommandBox> start cfengine=adobe@10.0.12

Start any Java WAR as a server

This goes hand-in-hand with multi-server support, but opens the door even wider to ANY Java J2EE application, which could be a custom CF engine build of your choice, or just a standard Java application.

CommandBox> server start WARPath=/path/to/explodedWAR
CommandBox> server start WARPath=/path/to/WARArchive.war

Global Server Defaults

You can store your server settings in a server.json file since version 3.0.0.  Now, we've made it even better by allowing you to provide global defaults that apply to all servers via the config settings.

CommandBox> config set server.defaults.app.cfengine=lucee@5-snapshot
CommandBox> config set server.defaults.jvm.heapSize=1024

New ForgeBox 2.0 API

We've re-written the ForgeBox API to be better, faster, and stronger.  It supports a whole slew of new functionality to help CFML developers publish their packages and get them into the hands (and servers) of other developers.

ForgeBox 2.0 tracks multiple versions of the same package

This is self explanatory, but a huge improvement.  Your project's entire history of releases can now be tracked via ForgeBox, allowing users to install the specific version of your package that they need.

CommandBox> install coldbox@3.8.1

ForgeBox can create users from the CLI

Signing up for a new ForgeBox account just got even easier with the following command.  

CommandBox> forgebox register

ForgeBox can log you in from the CLI

You can also authenticate to ForgeBox to publish your packages and more with this new command.  You may never touch a web browser as long as you live.

CommandBox> forgebox login

ForgeBox can publish package from the CLI

Put them all together and what do you get? Only the smoothest, fastest, and most advanced workflow for managing your open source packages in the CFML space.  With one command you can shoot new packages off to ForgeBox for the entire world to see, or just update a new version of an existing package.  There's no need to log into the web site and keep stuff up to date, this command does it all for you, including reading in your readme files.

CommandBox> forgebox publish

Bumping package versions auto-tags your Git repo

In our never-ending quest to improve the developer's workflow, bumping your packages to a new version will automatically tag your local Git repo (if you're using one).  That's one less thing you need to worry about before using the publish command.

CommandBox> bump --patch message="Finalized awesome features."

Semantic Version support

Now that ForgeBox is aware of all your packages versions, the CLI is also able to use fancy version ranges to install the versions you need and allow you to update easily to new compatible versions of your packages in the future.  We've implemented full NPM-style semver support.  Check out these new syntaxes supported for packages on ForgeBox.

# Latest stable version
CommandBox> install foo

# latest version, even if pre release (bleeding edge)
CommandBox> install foo@be

# A specific version
CommandBox> install foo@1.2.3

# Any version with a major number of 4 (4.1, 4.2, 4.9, etc)
CommandBox> install foo@4.x

# Any version greater than 1.5.0
CommandBox> install foo@>1.5.0

# Any version greater than 5.2 but less than or equal to 6.3.4
CommandBox> install "foo@>5.2 <=6.3.4"

Interceptor-based CLI scripts

If you want to piggyback additional commands to run at key lifecycle events for your package, servers, or CLI, you can specify scripts in your package.json.  Scripts are commands to be run from the CommandBox interactive shell, that will execute automatically in the same working directory.  They are stored in the box.json under an object called "scripts" and keyed off the name of the interceptor you want to fire them. These are useful for additional housekeeping tasks that you want to make automatic.

{
  "scripts" : {
   "postVersion" : "package set location='gitUser/gitRepo#`package version`'"
   "postPublish" : "!git push",
   "onServerStart" : "echo 'Hi, thanks for starting `server show name` on port `server show web.http.port` in directory `pwd`'"
  }
}

Well, don't just stand there

It's time for you to get out there and test.  Put in tickets for any bugs you find here.  To review, you can download the beta for CommandBox 3.1.0 here:

http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/3.1.0/

And if you want to read a more in-depth review of the features, check out these posts on my personal blog:

Exciting New Features In The CommandBox 3.1.0 Bleeding Edge

CommandBox Multi-Server Support Now In Beta (v3.1.0)

 

 

CommandBox, ForgeBox, Releases 0

CommandBox Now An Official Homebrew Formula

Jon Clausen
Feb 27, 2016

 

 

At Ortus, we try to make the installation of our tools as simple as possible, while supporting a variety of platforms.  For OS X users, staying up-to-date with your CommandBox installations just got a bit easier.   

CommandBox is now an official formula for Homebrew, the package manager for Mac users!

ColdBox MVC, ColdFusion, CommandBox, Tutorials 0

CommandBox 3.0.1 Released

Brad Wood
Feb 23, 2016

 

Today we are announcing a patch release of 3.0.1 for CommandBox CLI users.  This is a very small release that contains a single fix for those using the new server.json feature of CommandBox 3.0.0.  

New Stuff

Properties weren't being read correctly from the server.json file.  If you have been using server.json, please double check the format of the file here in our docs:

http://commandbox.ortusbooks.com/content/embedded_server/serverjson.html

This fix will make this functionality work as expected:

server set web.http.port=8000
server start

 Upgrading

If you already have 3.0.0 then this fix only affects the CFML bits and is very easy for you to install.  Simply run this command:

upgrade

If you're still on CommandBox 2.x, check out our 3.0.0 release announcement to see the cool new stuff.

CommandBox, Releases 0

Build, Test, and Deploy Your Module with Travis CI

Jon Clausen
Feb 15, 2016

 

In its early stages, shipping your new module isn't such a big deal.  The .zip link provided by GitHub works fine for the Forgebox link, and it's not a big deal to update the entry whenever you release a new version.  Once you release it and other developers actually start using and depending on your software, however, the need to automate aspects of the build and deployment process become apparent.  
ColdBox MVC, CommandBox, ForgeBox, TestBox 3

Box Training this March 2016 in Houston

Luis Majano
Feb 10, 2016

 

 
We are so excited to bring our Training Bootcamp series to the Houston area this March from March 30 - April 1st, 2016.  This training series will be led by Box creator Luis Majano.  Whether you are an MVC expert or novice, this bootcamp will challenge you and refresh your skills to the latest ColdBox, CommandBox and TestBox versions.
 
The first 2 days of the course will focus on a quick start with CommandBox for CFML development and transitioning to ColdBox 4 MVC and Modular Development.  Day 3 will focus on one of the most feared topics for developers: TESTING!  We will demistify Behavior Driven Development and introduce the necessary tools to make you a testing ninja.

 

ColdBox MVC, CommandBox, Conferences, Training 0

CommandBox 3.0.0 Final Released

Brad Wood
Feb 09, 2016

 

We are super excited to release CommandBox 3.0.0, our newest version of the CFML CLI, REPL, package manager, embedded server, and your source of awesome ASCII art.  This is a major release of the platform that contains many new features and improvements totaling over 50 tickets!  The final version is available for public consumption and we recommend all CommandBox users upgrade.  

Get It

As usual, the only step required to upgrade is to replace your 'box' binary and the next time CommandBox runs, it will complete the install. If you used yum, apt-get or brew to install, just request the newest version.  All the binaries are also available on our download page.

If you're new to CommandBox, no worries. Just check out our installation page where we have detailed instructions for each operating system to get you up and running in about 60 seconds.

https://ortus.gitbooks.io/commandbox-documentation/content/setup/installation.html

Got It

Once you've installed the latest 3.0.0 build, let's look around at some of the new stuff:

  • Config Settings - Customize and configure CommandBox just for you
  • Modules - The 'Box is now modular and can be extended like never before
  • Interceptors - Hook into the internals of the CLI and build upon it
  • Standardized Command Packaging - Custom commands can now be packaged up as modules
  • Server.json - Default every aspect of the embedded server for packaging and convenience
  • Shortcut for Native OS Binaries - Mucho improved native shell executions from inside CommandBox
  • Shortcut for CFML Functions via REPL - A new sweet way to run CFML functions right from the commandline
  • Expressions in Command Parameters - Express yourself with new syntaxes for calling commands with dynamic inputs
  • Command DSL - New features to help devs writing custom commands

There is a full write up on each of these features including examples and links to the docs here in our beta release post.  Please read through it if you want to dig in deeper to the new stuff.

http://www.ortussolutions.com/blog/commandbox-300-beta-released-for-testing

ColdFusion, CommandBox, Releases 0

CommandBox 3.0.0 Beta Released for Testing

Brad Wood
Jan 19, 2016

 

We've been hard at work developing some cool new features for CFML's CLI, Package Manager, REPL, and Embedded Server, CommandBox.  Since there are so many major features, we're targeting this as a major release of the product, so welcome version 3.0.0s.  We want you to kick the tires and try out the newest features before our final release.   Please put in tickets for any issues you run across, or post to our mailing list.

Installation

First things first.  To install the latest 3.0.0 beta version of CommandBox, download the appropriate binary for your OS here:

http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/3.0.0/

The first time you run box, it will install and replace any previous installation.  If you want to go back to the previous version later, you'll need to remove the .CommandBox folder in your user home first.

Documentation

The GitBook-based docs have had major updates made to them.  Prior to the final release of CommandBox 3.0.0, you can preview the bleeding edge of our docs here: 

http://commandbox.ortusbooks.com/content/v/development/

Also, the bleeding edge API docs are available here as well:

http://integration.stg.ortussolutions.com/artifacts/ortussolutions/commandbox/be-apidocs/

 

ColdFusion, CommandBox, Releases 0

DocBox 2.0.5 Released with Updated CommandBox Commands

Brad Wood
Jan 19, 2016

 

We are excited to announce the general release of DocBox v2.0.5 and our new CommandBox DocBox command module.  This release brings some great features for the creation of API documents, but also the tight integration into  CommandBox to allow you to generate API Docs with only CommandBox installed.  Below you can learn more about our release.

This update fixes the installation so you can install DocBox into your project by running the following Command using CommandBox:

box install docbox

The code repo and readme for DocBox is here:

https://github.com/Ortus-Solutions/DocBox/

We have also released our first final 1.0.0 version of the CommandBox Docbox command.  If you want to generate your API docs completely from the command line without the need to even start a server, this is for you! The CommandBox commands are stored in a separate repo as well.

https://github.com/Ortus-Solutions/commandbox-docbox/

Install the new DocBox CommandBox Commands and use them like so:

box install commandbox-docbox
box docbox generate source=/path/to/coldbox mapping=coldbox excludes=tests strategy-outputDir=/output/path strategy-projectTitle="My Docs"

 

Please note, these command require the latest CommandBox 3.0 beta which can be downloaded from our integration server or via the CLI as well by running the command box upgrade --latest

This should allow you to really add some spice to your build jobs with new and easier ways to generate your API docs via Docbox.

CommandBox, Releases 0
<< 1 2 3 4 5 6 7 8 9 >>