> So as not to inundate the user with the multitude of options provided > in the Administrator, for one, and to make sure that a user doesn't > change a particular setting or settings that your application relies > on, for another. Further, I wouldn't want to dump settings and stuff > in a production environment. While developers tend to "cheat" all the > time, a production environment should be a pristine version of your > application, devoid of all debugging code and settings.
I think our perspectives are different. Some of the software I develop is deployed in places I will never visit. At those locations, they often have development, QA and production systems. So, when I "deploy" an app, it's not straight to production. Deployment for me means that it's going to a customer's site. There's usually 6 months or so between the time the customer sets it up in development and the time the app goes into production. During that time, we're determining the best settings for the particular environment. Once we've set up the development environment, the customer (or on site consultants) duplicates it as QA environment and then as a production environment. > It's not a question of smart vs. dumb or lazy. It's a question of what > one is used to and whether or not they are willing to make the effort > to learn a different process to deploy a J2EE application. If I have > to log in to the JRun Admin Console to administer all my other J2EE > apps but then use the CFMX Admin just to administer my CF apps, that's > a bother to the sys admin, who, in large shops where standards are > prevalent, don't have time for disparate systems. One could argue both > sides quite convincingly, I'd wager, but at the end of the day, as I > mentioned earlier, this particular feature really caters to pure J2EE > admins as opposed to developers like you and me who are used to CF's > deployment experience. I agree, but I think we're also talking a difference in scale. The companies buying the software in question fly a team of people out to take classes to learn how to use the software. If these people couldn't learn how to use the ColdFusion Administrator, then they sure as heck can't learn how to use the rest of our app. BTW, the apps that I'm refereeing to are not written in CF. They are written in ASP and Java. But, they're the best basis I have for comparison. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193838 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
