> It was more the case that if ColdBox doesn’t match a domain it automatically loads in production
Actually, this behavior is up to you. I prefer to make my default ColdBox settings the production ones, and use the environment detection to switch over to local, dev, or stage. However, there’s nothing keeping you from reversing that by switching where you put your production settings.
Start by putting whatever collection of settings you deem “safest” in the default configure() method of coldbox.cfc. This way, if no other environment is matched, these settings will be used.
Next setup whichever process you want to use for sniffing out your production servers (host name, machine name, mac address, whatever) and put your PRODUCTION settings in a “production” method that ONLY gets called when you say. That way, dev settings are the default, and production settings are the exception. So when “Prod75” and “Prod438” get set up, they won’t use production settings until you explicity go and add them into the config as valid “production” servers.
Make sense?
~Brad
