Blog

Assembla migration complete

Luis Majano November 19, 2009

Spread the word

Luis Majano

November 19, 2009

Spread the word


Share your thoughts

I am glad to inform that all of our ColdBox platform projects have been successfully migrated to Assembla.  We are now starting to use all of our cool new tools and organizational elements.  So head on over to our new tracking homes!

Our next step is that we are migrating all of our documentation to our new wiki home based on CodexWiki.  This will be a great chance for us to eat our own dog food :) and also to keep updating CodexWiki in a more timely fashion.

Also remember that we can now host your ColdBox related projects in our own ColdBox Community Development space.  So if you need git/svn hosting with a nice ticketing and collaboration system, let us know.

Enjoy!

Add Your Comment

(3)

Nov 19, 2009 21:01:51 UTC

by Anastasia

Congrats! I know you'll love using Assembla. It made my life so much easier!

Nov 19, 2009 21:02:38 UTC

by Anastasia

Congrats! I know you'll love Assembla! It made my life so much easier when I switched.

Nov 24, 2009 10:27:04 UTC

by IsNotImportant

You made the right choice guys.

Assembla is the best way to go for distributed teams.

Recent Entries

Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern

Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern

Learning a new AI API usually means jumping between scattered documentation pages, guessing at imports, and copy-pasting code that may or may not still work. We wanted something better for BoxLang AI, so we built the BoxLang AI Explorer: a local, browser-based catalog of runnable BoxLang AI examples, organized by category and difficulty, each with guidance, source code, and sample output.

Luis Majano
Luis Majano
August 14, 2026
Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM

Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM

If you've spent years in Spring Boot, Micronaut, or Jakarta EE, "web framework" usually means a servlet container, an embedded Tomcat or Netty, a build step, and a fat jar before anything answers a request. What if you could skip all of that and still be on the JVM?

Luis Majano
Luis Majano
August 12, 2026