A Step-By-Step Guide To Install Railo Server 3.1 On Mac OS X 10.5 (Leopard)
When I was ready to install Railo server I hit up google to see how you would go about installing it on Mac OS X 10.5 (Leopard). There wasn't a lot out there. Actually, there was only one good article I could find, but it didn't allow me to do everything. I've decided to post the steps I took to install Railo Server on my Apple G4 running Mac OS 10.5 Leopard. But first, I have to give credit where credit is due. I based this entire article on what I found here at Luis F. Majano's blog. Everything is built upon this post. Thanks Luis!
The goal of this install is to get Railo running on my server and to have all web files located in a common folder and accessible from the outside internet. I need to do this, so my clients can check their site as I am developing them. I have not tried installing PHP or Adobe ColdFusion server along side Railo. This is something I may look into down the road.
- Here's a quick list of my setup:
- Apple G4 Server running Mac OS X 10.5.8
- Railo 3.1.1 w/Resin for Apache (www.getrailo.org/index.cfm/download/)
- MySQL 5.1.38 (This is not really important for this tutorial, just listing what I'm using)
You are going to need to have a text-editor of some sort, I use BBEdit. It allows me to edit hidden/protected files, by providing my Admin password. I'm going to assume that you can figure out how to edit these files if you plan on using something else. You are going to need to use the Terminal.app (don't be scared, I'm by no means a Terminal master). And finally, you are going to need to have XCode installed on your development machine in order to make the install the Railo Apache connector. And lastly, you need to be logged in as an Administrator. I don't think this will work, if you cannot do this.
This may seem obvious to some, but just in case, you also need to have Apache running. To do this, you need to open up System Preferences > Sharing. Make sure that Web Sharing is checked. You can test if Apache is working by pointing your web browser to your server (localhost or 127.0.0.1 if it's on the machine locally) and see if you get the default Apache welcome screen. If it is, your ready to roll. If it's not, then you need to get that working before you can continue.