ForgeBox Updates — September 2017

Eric Peterson September 11, 2017

Spread the word

Eric Peterson

September 11, 2017

Spread the word

Share your thoughts

Happy Monday! We have a new release of ForgeBox to walk you through today. I think you'll like what we have for you as it makes using ForgeBox day to day so much nicer.

First, a quick note about me and the ForgeBox project. I recently joined the Ortus team full time and have taken the reins as developer evangelist for ForgeBox. This release of ForgeBox was focused around polishing some rough edges. It was also the perfect way for me to get my feet wet in the project.

A New ForgeBox Release

Here's what we worked on and is available in today:

  • We've eliminated (at least one of) the dreadful JDBC Batch Error messages. Side benefit, you can now store very long blocks of text as well as emoji (?) in the Description, Installation Instructions, and Changelog fields. (Also, remember to set your database character encoding right for kids these days. ?) (FORGEBOX-122)
  • We've updated cbmarkdown to use a new engine underneath. This let us enable more Markdown features like tables. (See an example of that here.) Don't forget to update your projects as well! (FORGEBOX-127)
  • Sorting packages by Updated was sorting by any package change, not just new versions. This meant that updating a package's description, tags, or even just registering an install or download would cause the package to be register as Updated. This behavior has been fixed and now only new versions will register as Updated. (FORGEBOX-131)
  • Small pet peeve of mine, but now searching for packages won't have a double // in the url. It didn't break anything, but just looked off. (FORGEBOX-103)
  • Also a pet peeve, the broken Disqus links are now fixed server-side. (FORGEBOX-100)
  • When searching for packages, a logged in user can see their own inactive packages in the search results. This is super nice if you, like me, wondered where that package you just made disappeared. (FORGBOX-123)

Additionally, private packages continue to get a lot of love. We've done another round of updates with input from you, our beta testers! (Thank you!)

  • Private packages created from CommandBox were not always flagged as private correctly. Now they are. (FORGEBOX-126)
  • To make private packages look more consistent, we're migrating all usernames to a new format.
    • Usernames can now only contain letters, numbers, hyphens, and underscores. (FORGEBOX-130)
    • You can now update your username from your profile. Updating your username will automatically update your private package slugs as well. However, no redirects are provided from your old private package slug to the new ones. (FORGEBOX-129)
    • The next time you log in to the ForgeBox website or hit the API from CommandBox, if your username does not match the new requirements, you'll be asked to update your username before proceeding. You must update your username before interacting further with ForgeBox. (FORGEBOX-128)

We appreciate your help changing your username. We feel it will help the ecosystem have a better visual feel. is just harder to look at than @foo-example/my-package.

Coming Next

Let me finish by giving you a sneak peek at what's next for ForgeBox!

  • Private Package Subscriptions
  • Ortus hosting of private packages
  • Collaborators for both public and private packages


Have feedback on the release, what's next, or ForgeBox in general? Drop us a note in the CFML Slack in the #box-products channel or comment or create a ticket in the ForgeBox Jira!

Add Your Comment

Recent Entries

October is here, and that means Hacktoberfest!

October is here, and that means Hacktoberfest!

Hacktoberfest is here!

Ortus Solutions is built upon Open source with our flagship products all open source, this event holds a special place in our hearts and it’s a great space to show developers how we are modernizing the CFML language. We invite everyone to get involved and contribute to CFML Community Projects, with documentation, code, and new this year, non-code contributions. 

Maria Jose Herrera
Maria Jose Herrera
October 04, 2022
Using CommandBox Docker Images to Perform Bytecode Source Conversions

Using CommandBox Docker Images to Perform Bytecode Source Conversions

There are times when code needs to be shipped in a compiled state. It might be for obfuscation or source protection, it might just because it runs faster that way, without the CFML server needing to compile templates at runtime. It's an excellent use case for production Docker images and code deploy pipelines.

Jon Clausen
Jon Clausen
October 03, 2022
cbElasticsearch 2.3.3 Released

cbElasticsearch 2.3.3 Released

We are pleased to announce the release of cbElasticsearch version 2.3.3. cbElasticsearch is the Elasticsearch module for the Coldbox platform, and provides a fluent CFML API for interacting with, searching, and serializing to Elasticsearch servers.

This release adds full compatibility for Elasticsearch v8.x as well as maintaining support for Elasticsearch versions 6 and 7.

Jon Clausen
Jon Clausen
October 03, 2022