MAC [SINGLE SERVER] VERSION WOES 

I note that Ken's on a Mac. So I tried it on a Mac too. The OPML Community Server does not seem to be picking up port 80. I've disabled the built-in Apache through the Web Sharing service, which is annoyingly tied to the firewall on OSX, meaning I don't seem to be able to enable port 80 on the firewall without switching on the Web Sharing service, which invokes Apache! Argh! Still with me? Phew!

When Apache is off and I launch the OPML Editor with the Community Server enabled, I can register and login fine. Files are created. It's all good.

But if I open up my built-in Network Utility on OSX (in Applications / utilities ) and do a portscan on my local ip (127.0.0.1) I can see that port 80 is not in use. (It does show as in use when I start Web Sharing again)

update: Interesting reading I tried this method ie: launching OPML from the terminal, as root. Still no port 80 yet.

update: I found this interesting PDF from the Frontier and Manila user Guides (url to html rendering via google) and it talks about the issue of only having one IP address and being stuck on a Mac with it's builtin Apache (which works)

Here's the juicy bit:

Mac OS X and Apache

There are two more solutions if your server is running MacOS X and Apache:

1. You can configure MacOS X to use two IP addresses, and then set up Apache to listen on one IP address on port 80, and Frontier to listen on the other IP address, also on port 80. This is a little complicated to set up, but will give nice results.

2. If multiple IP addresses are not an option, and you need to keep Apache running, then it's possible to configure Apache to act as a proxy for requests that are intended for Frontier/Manila. This requires that you do a little work in your apache.conf file (Apache's configuration file), to tell Apache how to forward the requests. There's some additional tips on this setup from the Frontier for Mac OS X site.

The advantage of the second approach is that you get seamlessness between Frontier and Apache running on the same IP address (or domain name), but the disadvantage is that depending on how you'll use Frontier, you'll need to add a few lines to apache.conf for each new site you create.

more reading : An interesting thread on on the Frontier site called 'coexisting with apache on same server'

even more reading on Frontier and Apache behind one port

Question : Has Dave tried it on his own Mac?

|

OPMLCS UPDATE 

No change on the status of my OPML Community Server. I don't know of anyone else who has one running. Looks like we'll have to wait some more.

Sometimes this feels like a painful way to test stuff out, without proper instruction and explanation. It will come. But I think I'm going to wait for someone else to do the legwork on this - possibly someone the creator of software can speak to without flipping a lid. ;)

I might fiddle a bit here and there, but I don't feel comfortable helping out at this stage. If my time and help is required, one person out there knows what to do. Make the peace.

I note that Ken Tompkins seems to be the closest. I think he could make his like alot easier if he was to point some real subdomains to his address and use those for the rpc, blogs and host settings. The system seems to be messing up his destination urls.

Ken: if you don't have domain you can use, drop me a line and I'll point some subdomains your way for you to test with.

HO HO OOPS 

Ha ha. Oh dear. Another one refuses good advice and bites the dust (temporarily but annoyingly). Some people just don't listen or read (to the complaints about iTunes etc).

I have copies of music in various formats I bought years ago, as I am sure many have. I can still play them on a multitude of devices. They didn't 'expire' or become useless. Apart from the 8-Track tapes :) hehe.

   Subscribe to this blog feed

   

November 2005
Sun	Mon	Tue	Wed	Thu	Fri	Sat
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30