This is how you can configure Railo Express to use Jetty virtual hosts and local host file entries to point to a single Railo Express installation. This was extremely useful while developing applications that power multiple domains.
-
Archives
This is how you can configure Railo Express to use Jetty virtual hosts and local host file entries to point to a single Railo Express installation. This was extremely useful while developing applications that power multiple domains.
Today I wanted to setup local host entries on my MacBook. Searching around I found several articles about editing the /private/etc/hosts file to add local domains entries pointing back to my computer. I don’t know if it is something that changed with Leopard or Snow Leopard but it just wasn’t working for me. Even restarting the computer was a no go.
One of the things that I was really excited for in ColdFusion 9 was the support for the ternary operator. As Ben said:
To me, the ternary operator is what the IIF() method call always wanted to be.
Unfortuately I was testing some CFML code, written and working on Railo, on a ColdFusion 9 server and had this error pop up:
Unable to find an operator implementation for coldfusion.compiler.ASToperator
Turns out the the ternary operator works great… unless you are using it in a default value for an argument. Fail.
Here is how I setup a VirtualBox Virtual Machine (VM) running Ubuntu 9.10 Server edition for ColdFusion development on my MacBook Pro.
There was a bug in Jetty that was causing MXUnit ant tests to not work because it was double encoding the cookies. The bug was fixed in Jetty but Railo had not released a new Express version with the fix.
Many of the domains and sub-domains on my Media Temple Grid Service contain installations of WordPress. Since I don’t want to be bothered by a normal upgrades here is how I install WordPress in a way that allows for simple upgrades.
This is not a completely automated solution, there is more that you could do to improve the process, but it should save a lot of the time normally spent updating WordPress.
While working on an AIR project hosted on Google Code I wanted to setup automatic updates. I wanted the entire project to be self contained and not require any supporting websites. After a little coding I can now use Mate and dispatch an event to check for updates.
As I amass more photos I get squeamish. Photos are some of the most valuable data on my computer besides the code I write. My code generally isn’t a big worry because it is being versioned and usually exists in several working copies so the risk of loss is smaller. With photos I have at best have a dvd backup of the originals along with a time machine backup. But if my apartment and computer goes up in smoke? It’s all gone.
With the wonderful advances in the cloud I decided to see what it could do for me. After doing a little searching I found a post or two about it and I decided to try it out myself.
I am a terminal n00b, but I’m liking it. I grew up on a M$ box and didn’t take the ‘leap’ to a linux / unix based operating system until about a year and a half ago when we got new computers at work. Since that time I have been trying to learn more about the terminal and am very impressed by it. I’ve been using OS X at work and Ubuntu at home and haven’t booted into windows (except for playing games) for almost a year.
Something that I found out in the recent months and finding very useful is the reverse-i-search. By pressing ctrl + r in the terminal (works at least in ubuntu and OS X, probably all real terminals) you are given a console line like the following:
(reverse-i-search)`':
As you type the terminal will search through your terminal history and locate any commands that contain what you search.
Sitemaps just make sense. You create a Sitemap file, or a set of files and a Sitemap Index, that has all the your site links crafted purely for search engine consumption. It’s like candy for the search giants since they get spoon-fed your site structure by you. Not only can it tell them where your content is, but it can tell them how often it changes, when it was last changed, and what priority it is to your site. Pure confection!
But the problem, for me at least, was finding the urls to ping so that you are not waiting for the giants to get a sweet tooth and come looking for you. The page on informing giants talks about a magical searchengine_URL that can be replace by your supporting giant. The problem: the site never tells what searchengine_URLs exist for your giant companions.