Posted At : February 5, 2010 1:30 PM | Posted By : Bob Silverberg
Related Categories:
ColdFusion,OS X,Apache
I've been trying, on and off, for nearly six months to get two versions of ColdFusion, CF 8 and CF 9, running in a MultiServer install of CF with JRun on my Mac.
I've read all of the
documentation that is available, as well as a good number of blog posts, but I always seem to get stuck at the point of deploying my CF9 EAR into my existing copy of JRun
(which was installed during the MultiServer install of CF8). Everything I've read suggests that auto-deploy should work - you just copy your exploded EAR into a folder under JRun/servers/
and JRun will deploy CF9 for you. Well, for whatever reason, that simply does not work with my setup.
I also tried to manually deploy (in spite of there seeming to be zero documentation on how to do that), but still could not get my instance of CF9 to start up in JRun.
After walking through all of the steps yet again yesterday, and coming up with the same result, I asked someone who in my mind is the most knowledgeable person about this topic,
particularly when it comes to OS X, Sean Corfield. We discussed the steps I had taken, and he suggested that auto-deploy with JRun
can be problematic. He then suggested a solution that worked perfectly for me, so I'm going to share it with you here.
[More]
Posted At : November 4, 2009 11:39 AM | Posted By : Bob Silverberg
Related Categories:
OS X,Git
This post is a follow-up to my earlier post about Placing Config Files Under Version Control with Git and GitHub. In that post I discussed how one can use Git and GitHub to place your config files under version control (via Git), and to maintain a backup of them (via GitHub). In this post I'm going to discuss a set up that will allow another machine's config files to stay in sync with the originals. The scenario I'm discussing involves config files, but one could use this approach for any set of files that one wants to keep in sync between two machines.
[More]
Posted At : October 30, 2009 1:39 PM | Posted By : Bob Silverberg
Related Categories:
OS X,Git
Working with Git, I've become aware of the fact that there are certain config files on my machine which require customization and therefore would be nice to have under version control. These files are often referred to as dot files, or dotfiles, as their names all start with a dot. The three files that I currently have under version control are .bash_profile, .gitconfig and .gitignore. The first two of those files expect to reside in my home directory, but the way Git works, in order to place them under version control they need to reside in a folder that is also a Git repository.
For obvious reasons I don't want to make my home directory a Git repo, but there's a simple solution to this problem. Using symbolic links, a topic that I discussed in an earlier blog post, I can keep my dotfiles in a Git repo, and also continue to use them as live config files.
Here is a step-by-step guide to getting your dotfiles under version control with Git:
[More]
Posted At : October 30, 2009 9:36 AM | Posted By : Bob Silverberg
Related Categories:
OS X,bash
Although I'm just starting to discover the power of the CLI, I have used it in the past for creating symbolic links, which come in handy in a number of scenarios.
What is a Symbolic Link?
A symbolic link, or symlink as it's often called, is a special kind of file that points to and acts like another file or folder. You can think of it as kind of like a shortcut. Your Mac will treat it like a file or folder, and it therefore allows you to pretend to have the same file or folder in more than one location. When you look at a file listing in Finder, symlinks appear with a little curved arrow in the lower left-hand corner of the icon, and the Kind column reports that the file is an Alias, but it actually isn't.
[More]
Posted At : October 28, 2009 1:56 PM | Posted By : Bob Silverberg
Related Categories:
OS X,Git,bash
I've been working on a Mac for around four months now, and never really had much reason to open up Terminal and use the command line interface (CLI), other than for starting and stopping Tomcat. Now that I've started trying to learn about Git, I'm using the command line more and more, and finding out new stuff daily, so I'm going to write the occasional post to share some of this info.
About Bash
The operating system that most of us run on Macs is called OS X, and it's based on Unix. The way that one interacts with Unix is via a command shell, and the default shell for OS X is called Bash. It allows us to interact with our operating system without going through the graphical user interface (GUI) that sits on top of the OS. According to Wikipedia Bash stands for Bourne-again shell as it is a successor to the Bourne shell. So, when you open up Terminal, or iTerm which is an enhanced Terminal alternative, you are interacting with the Bash shell.
[More]
Posted At : September 15, 2009 4:57 PM | Posted By : Bob Silverberg
Related Categories:
OS X,CFEclipse
I just upgraded my MBP to Snow Leopard and I found that Eclipse would no longer start on my machine. It turns out that I had some custom settings in my eclipse.ini file, that I had picked up from a blog post by Marc Esher. Those settings did help speed up Eclipse, but one of them also prevented it from starting after the 10.6 upgrade.
I removed the offending option, -XX:+UseParallelOldGC, from my eclipse.ini file and now Eclipse is up and running again!
