Blog

Brad Wood

November 01, 2012

Spread the word


Share your thoughts

 

One of the first things you learn with ColdBox is how to add ?fwreinit=1 to the end of your URL to force a reload of the entire application.  This is required to pick up new settings, etc.  Many of you probably leave the reinit password at its default of "1".  While that's fine for your development and testing servers, it's not recommended  on production.  Reinitializing your application can potentially be an intensive operation, and you don't want someone out there having the ability to screw around with your app.  
 
Adding a little piece of mind is easy.  All you need to do is add a "ReinitPassword" setting in your config.
 
coldbox = {
    reinitPassword = 'passw0rd'
};
 
With that in place, you can now reinit the app like so:
 
http://www.yoursite.com?fwreinit=passw0rd
 
Remember, for the new password to take affect, you have to reinit the site one last time with the old password (which is cached in memory).
 
There you go!  You can sleep a little better at night knowing random people can't reinitialize your servers.
 
 
P.S. Do you only want the password on your production servers?  Easy-- just use the environment control I talked about last week.  Set up the production password in your main configure() method.  Then in your development or stage override methods, set coldbox.ReinitPassword back to an empty string.
 
 

Add Your Comment

Recent Entries

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025