One of the first things a beginning ColdFusion developer realizes, at least after their first few applications, is that configuration is something you want to make as easy as possible. What do we mean by configuration? Well imagine your web site has various forms. Forms for product reviews. Forms for job applications. Forms for budding Jedi Masters. You can build all of these forms so that on submission, they email to some email address, let’s say email@example.com. This is all fine and good until the client says, “Hey, can we have all forms go to firstname.lastname@example.org instead?” So, if you are using a decent editor, this isn’t a big deal. But obviously a multi-file search and replace isn’t the answer.
What you need is a config file, son! (Funny, and off-topic story on where that quote came from later on.)
What do we mean by a config file? A config file is a human-readable file that contains configuration information about the application. A perfect example is the scenario we described above. If the “Send All Forms Here” value had been in a config file, it would have been even easier to update the value based on customer demand. It may even have been something the client could do! (Yes, I know, scary, but it’s ok. Clients are perfectly ok working with files as long as take deep breaths and type very slowly.)
There are a couple different ways we can create a config file. For this first post, we are going to start with the venerable “ini” file format. (Don’t worry, the XML example will be in the next post.) What is an ini file? Ini files have been a part of Windows for many years. Scientists have reported discovering early versions of ini files buried deeply under prehistory middens. Basically they are text files with name/value pairs. Here is a simple example:
Simple enough, right? Along with name/value pairs, an ini file will be separated into sections, using bracket notation. Every ini file will have at least one section. Here is a simple example:
In the ini file above, there are three sections: live, staging, and dev. (I’ll talk more about these sections in my third post.) Each section has an email entry with a different value. My application can select the email key from any section it wants to, or load them all up.
So how can ColdFusion use ini files? ColdFusion comes with a set of built in functions to read and write ini files: GetProfileSections, GetProfileString, and SetProfileString. Let’s start by defining a simple ini file. Take the code below and save it as test.ini.
Now let’s look at how we can read the file. We will begin with a simple example of getProfileString:
<FONT COLOR=MAROON><cfset email = getProfileString(iniFile, <FONT COLOR=BLUE>"default"</FONT>, <FONT COLOR=BLUE>"email"</FONT>)></FONT>
<FONT COLOR=MAROON><cfoutput></FONT>Email=#email#<FONT COLOR=MAROON></cfoutput></FONT>
The first line simply creates a full path to our ini file. The first attribute that getProfileString expects is the full path to the file. (Am I the only who wishes that more ColdFusion functions would allow for relative paths?) The second argument we pass is the name of the section. In this case, we know it is default. Lastly we tell the function what key to retrieve. If you run this example in your browser, you will see my email address. (Spam away, folks.)
What happens if you pass a section or a key that doesn’t exist? No error is thrown. Instead you get a simple empty string. You could example the ini file before hand using getProfileSections:
<FONT COLOR=MAROON><cfdump var=<FONT COLOR=BLUE>"#getProfileSections(iniFile)#"</FONT>></FONT>
The function getProfileSections returns both the sections of the ini file and all the keys within that ini file. Since our ini file had one section, our returned structure will have one key, “default”. Because that section had one key, “email”, the value of the struct’s “default” key will be “email”:
So we can now read ini file settings. Obviously you would want to store and cache these settings:
<FONT COLOR=MAROON><cfset iniFile = expandPath(<FONT COLOR=BLUE>"./test.ini"</FONT>)></FONT>
<FONT COLOR=MAROON><cfset sections = getProfileSections(iniFile)></FONT>
<FONT COLOR=MAROON><cfset data = structNew()></FONT>
<FONT COLOR=MAROON><cfif structKeyExists(sections, <FONT COLOR=BLUE>"default"</FONT>)></FONT>
<FONT COLOR=MAROON><cfloop index=<FONT COLOR=BLUE>"key"</FONT> list=<FONT COLOR=BLUE>"#sections.default#"</FONT>></FONT>
<FONT COLOR=MAROON><cfset data[key] = getProfileString(iniFile, <FONT COLOR=BLUE>"default"</FONT>, key)></FONT>
<FONT COLOR=MAROON><cfset application.settings = data></FONT>
<FONT COLOR=MAROON><cfthrow message=<FONT COLOR=BLUE>"Ini file has a missing default section!"</FONT>></FONT>
<FONT COLOR=MAROON><cfdump var=<FONT COLOR=BLUE>"#application#"</FONT>></FONT>
What’s going on here? First we check to see if an application variable called settings is defined. If it isn’t, or if we pass in a special URL variable to refresh the cache, we know we need to load our settings. We use getProfileSections to first load up the sections from the ini file. After checking to see the there is a default section, we loop over the keys from the section and copy over the values. The data structure is basically a copy of all the name/value pairs from the ini file. Once done with the loop, we copy them over to the application scope. Notice we also do a bit of error checking. If for some reason the default section doesn’t exist, we immediately throw an error. This makes sense if you think about it - if the application isn’t properly configured, we should stop everything.
So, the last function we need to talk about is setProfileString. As you can probably guess, this allows you to update an ini file. It takes four arguments: The name of the ini file, the section, the key, and lastly the value. I’m not really going to bother with an example of this since I don’t find myself updating ini files from code very often. In fact, I’ve never done it. But it is there if you need to.
In my next entry (most likely not till Monday) I will discuss using XML files for application configuration.
So, this was my first 101 posting. Too much? Too little? Be critical!