gitignore Addition of ColdBox HMVC Framework

Reasons for making this change:

Adding support for the ColdBox HMVC Framework for ColdFusion (CFML)

Links to documentation supporting these rule changes:

https://coldbox.ortusbooks.com/

If this is a new template:

Link to application or project’s homepage:
https://www.coldbox.org
https://github.com/coldbox/coldbox-platform
https://community.ortussolutions.com
https://coldbox.ortusbooks.com/

Feb 04 '21 19:02 lmajano

This PR is stale because there have been no updates in 90 days. It will close after 180 days of inactivity. Leave a comment if you want to keep it open :smile:

Jun 03 '25 16:06 github-actions[bot]

It's stale, because the code reviewers don't review! It has ONLY been four years.

Jun 03 '25 16:06 lmajano

We typically don't house gitignore templates for frameworks in our root directory. How would you feel about moving this to community/Coldfusion/ColdBox.gitignore?

Jun 06 '25 22:06 wirecat

Thanks so much for the feedback @wirecat . I updated the ignores to the latest versions.

How would you feel about moving this to community/Coldfusion/ColdBox.gitignore? ColdBox is an MVC framework for two languages: BoxLang (www.boxlang.io) and CFML. So it would have to be for both?

With that said, you have already 36 frameworks in the root?

Angular - JavaScript frontend framework
CakePHP - PHP web framework
CodeIgniter - PHP web framework
Concrete5 - PHP CMS/framework
CFWheels - ColdFusion web framework
Drupal - PHP CMS/framework
ExpressionEngine - PHP CMS/framework
ExtJs - JavaScript framework
FuelPHP - PHP web framework
Grails - Groovy web framework
Jekyll - Static site generator/framework
Joomla - PHP CMS/framework
Kohana - PHP web framework
Laravel - PHP web framework
LemonStand - PHP e-commerce framework
Lithium - PHP web framework
Magento - PHP e-commerce framework
Nanoc - Ruby static site generator
Next.js - React-based web framework
OpenCart - PHP e-commerce framework
Phalcon - PHP web framework
PlayFramework - Scala web framework
Plone - Python CMS/framework
Prestashop - PHP e-commerce framework
Qooxdoo - JavaScript framework
Rails - Ruby web framework
SeamGen - Java web framework
SugarCRM - PHP CRM framework
Symfony - PHP web framework
SymphonyCMS - PHP CMS/framework
Textpattern - PHP CMS/framework
TurboGears2 - Python web framework
Typo3 - PHP CMS/framework
WordPress - PHP CMS/framework
Yii - PHP web framework
ZendFramework - PHP web framework

Jun 09 '25 12:06 lmajano

@lmajano we haven't always got it right, but we're trying to uphold the standards passed down to us from previous maintainers.

In some of the examples you've provided, those frameworks definitely don't feel like the right fit in root to me now, but someone made that call back in the day. Rails and WordPress feel like good examples that I would commit to root, as they are extremely common frameworks in the industry.

If you feel ColdBox should be placed in root, we need good justification on why. Does it have a large userbase? Lots of forks? etc. I see it being used, but it hasn't quite reached the level of widespread use that would make me pull it into root.

It's unfortunately rather subjective, but it's the best we can do to prevent root from being flooded with templates.

Jun 13 '25 20:06 wirecat

Thanks so much for the thoughtful response, @wirecat — I really appreciate the stewardship you're providing for the project and your desire to avoid bloat in the root. It sounds like you’re trying to maintain a high bar for inclusion, which I completely respect.

It seems like the concern is whether ColdBox has the kind of adoption and ecosystem to justify root placement — is that fair to say?

ColdBox has been the de facto standard MVC framework for the CFML language for more than 20 years and, as of 2024, it also supports BoxLang, a modern JVM dynamic language designed for multi-runtime environments. It's been around for nearly two decades, with a rich ecosystem of libraries, tooling, and educational resources. It has become central to how many developers build web apps and APIs in the CFML and JVM spaces.

What’s the best way forward from your point of view?

Jun 16 '25 08:06 lmajano

It seems like the concern is whether ColdBox has the kind of adoption and ecosystem to justify root placement — is that fair to say?

That is correct and I'm open details demonstrating the widespread usage. I'm not a CFML or ColdBox user myself so I have to rely on documentation, usage on GitHub and other platforms, etc.

Could you quantify usage in someway that would demonstrate it's usage and popularity? Are there artifacts in GitHub, or another public sites, we could reference?

I'm open to almost anything other than purely anecdotal evidence. We unfortunately receive too many requests for additions to rely purely on the authors word.

Jun 20 '25 21:06 wirecat

Sorry, was on PTO, back now.

As far as popularity, you can even do a Google search and discover all the history around the platform since it's release in 2006. There are major companies using it and some are not in GitHub like: NASA JPL, NASA Ohio Center, NASA Kennedy, Air Force, US Navy, FAA, L'Oreal, Adobe, Notre Dame, Virginia University. I mean, we have thousands of customers using ColdBox for both external and mostly internal applications (www.coldbox.org).

https://www.google.com/search?hl=en&q=coldbox%20framework

Would this be sufficient?

Jul 02 '25 15:07 lmajano

@lmajano I'm sorry but it's still quite hard to gauge popularity based off a google search. I would be much more comfortable housing this template in community/Coldfusion/ColdBox.gitignore like suggested previously.

Jul 25 '25 21:07 wirecat

No problem @wirecat I am ok with adding it to community and then later on we can re-evaluate. I have added it to two folders, since ColdBox is a framework for 2 languages.

Jul 28 '25 09:07 lmajano