The Ortus BlogBox

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

 

 

Category Filtering: 'forgebox'

 

ForgeBox v2.2.0 Released

Luis Majano
May 24, 2017

 


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!

Bugs Squashed

Improvements

  • [FORGEBOX-96] - Add some error logging for "Valid JSON not received in POST body."
  • [FORGEBOX-98] - sorting by popular is useless
  • [FORGEBOX-99] - Last publish date is not accurate
ForgeBox, News, Releases 0

Easy custom site host names with CommandBox

Luis Majano
Feb 14, 2017

 

In this video Brad Wood introduces the CommandBox Host Updater Module written by Chris Schmitz: https://www.forgebox.io/view/commandbox-hostupdater which allows you to automatically add host entries to your operating system and starting servers all on port 80 for you using CommandBox. It is really a great example of a CommandBox module, but also a great tool to have for ALL your ccustom development work. Enjoy!

Video

Installation

To get started with this module, simple use your CommandBox console to install it and running: box install commandbox-hostupdater. That's it, enjoy!

CommandBox, ForgeBox 3

Ortus Joins Patreon, Help Sponsor Open Source

Luis Majano
Aug 22, 2016

 

We are excited to announce we have joined !

Sponsor Us
 

At Ortus Solutions we are known for building open source projects for the ColdFusion (CFML) community such as ColdBox, CommandBox, ContentBox Modular CMS, ForgeBox and many more. All of those products are licensed under the Apache 2 license and are completely FREE to use and extend.

 

However, the amount of effort needed to maintain and develop new features for all projects is not sustainable without proper financial backing. This is where you can come in and help support Ortus Open Source Software by pledging on Patreon. We have listed a bunch of options for you to sponsor Ortus Open Source Projects with lots of rewards like getting awesome recognition and some great discounts, swag and t-shirts. By pledging as little as $10 a month, you can contribute to this great cause and allow Ortus Open Source to have faster and ongoing development cycles. Pledge more and you can even be part of our product roadmap planning sessions.

 

If you run a business and are using Ortus Open Source software in a revenue generating product or service, it makes sense to sponsor Ortus Open Source Software development: it ensures the project that your product/services use stays healthy and actively maintained. If you are an individual user and have enjoyed the productivity of our Open Source Software tools, consider donating as a sign of appreciation :).

Sponsor Us
 

CacheBox, CFCouchbase, ColdBox MVC, ColdFusion, CommandBox, Community, ContentBox CMS, Elixir, ForgeBox, LogBox, News, Relax, WireBox 0

CommandBox v3.1.1 Released

Brad Wood
Jul 01, 2016

 

We are pleased to announce the general availability of CommandBox 3.1.1 Final.  This is a minor release of our CLI tool,  but with some major new features.  We actually made the final 3.1.1 builds public a couple weeks ago for Into The Box, but have just now finalized the documentation and press release.  

CommandBox, ForgeBox, Releases 0

ContentBox 3 - Modules modules everywhere - Extending ContentBox

Gavin Pickin
May 18, 2016

 

In the last blog post, we talked about extending ContentBox with modules. With ContentBox being built on top of ColdBox, and integration with ForgeBox using CommandBox, there are a lot of modules ( and module locations), and how those modules interact isn't obvious at first. To be honest, with ContentBox 3, we only just decided to move the core contentbox modules, to provide clearer separation, and easier source control management... things are changing, so I thought this would be a great time to explain about the different type of module locations, and why you should use one over another.

CommandBox, ContentBox CMS, ForgeBox 0

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

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

Intro to box.json

Nathaniel Francis
Feb 26, 2015

 

In ForgeBox package management, the box.json file contains data related to your package. This post covers a good base for what minimum attributes to include to get your package loaded up to ForgeBox and make it CommandBox friendly.

CommandBox, ForgeBox 0

CommandBox - Searching ForgeBox

Brad Wood
Feb 09, 2015

 

We have big plans for using CommandBox to install packages from all sorts of code endpoints-- local folders, Git/SVN URLs, private corporate repos, etc.  Version 1.0 of CommandBox focused on ForgeBox though, which is our CFML code depot.  It may have started out as a ColdBox/ContentBox-specific thing, but is now open to the entire community to put any project they want on.  I'm excited to already see entries like CFWheelsFW/1MXUnit, and MonkehTweets on there.  The more packages installable from CommandBox via ForgeBox, the more we all win.

Soon ForgeBox will get even more life of its own enhancing it with more functionality such as having multiple versions of the same package. We've already set up forgebox.io as the new domain for ForgeBox's HTML interface where you can search, sort, and filter the entries in your web browser.  We've also built a "forgebox" namespace into CommandBox that uses the REST API to let you interact with ForgeBox from your console.

CommandBox, ForgeBox 0
1 2 3 >>