Two "bugs" located Permanent link to this item in the archive.

I can't really say if these are "bugs", per se.

In opml.root -> suites.opmlServer.startup

 I think the line:

 if user.opmlServer.ipAddressPort80 != -1

 is responsible for the trouble people had in the one server/one IP setup when they set a value for user.opmlServer.ipAddressPort80

 

 And the line:

 adrdata^.prefs.url = "http://" + user.opmlServer.hostname + "/"

 is responsible for my not being able to permanently change the blog and hosting server port to something other than 80.

Bug? Permanent link to this item in the archive.

If you change communities and use a different username/subdomain, if you switch back to your previous community, the username/subdomain does not update at: dotOpmlData.blog.prefs.baseurl.

Amyloo - I was thinking that a Hamachi VPN would be absolutely perfect for a private community. Then you could have users in your LAN and on the Internet, too. Permanent link to this item in the archive.

Looks like we made it Permanent link to this item in the archive.

Kosso and I seem to have hammered out how to get the OPML Community Server running on a one server/one IP setup. But that's only half the battle.

Now, we've got to write up a HOWTO.... I'll take a crack at a first draft:

You can try doing this without first performing a fresh installation, but fresh is best. Be sure to back up or make note of any modifications you've made to the object database that you want to keep.

HOWTO

0. All these instructions should be performed on the machine that's going to be the server. The software runs on either Windows or Macintosh operating systems; Windows 2000 or greater; Mac OS X. If you are making your server available on the Internet, ports 80 and 5337 must be open on the server. If you're behind a firewall or NAT router, you'll need to open a hole and/or forward the ports.

1. Download and run the OPML Editor from support.opml.org. Click on Cancel to the two dialogs that appear. Choose Get Latest Code from the Community menu.

2. In the OPML Editor application folder, create a text file called opmlStartupCommands.txt, containing the following four lines:

 user.opmlserver.enabled = true;
This tells the editor that it's a server. No modification necessary.

 user.opmlServer.rpcName = "RPCsubdomain.yourdomain.com";
The domain name used by the RPC server. This is the server that users connect to on port 5337 and the name is that which users will type into the "Change Community..." dialog to join your community.

 user.opmlServer.hostname = "HOSTINGsubdomain.yourdomain.com";
The domain name for used to serve static files, such as your header graphic, RSS XML, and unrendered OPML files. This must be different from the user.opmlServer.blogsname value.

 user.opmlServer.blogsname = "BLOGsubdomain.yourdomain.com";
The domain name people will type into their browsers to access your site. This must be different from the user.opmlServer.hostname value.

 Do NOT include a setting (even a NULL or empty string) for user.opmlServer.ipAddressPort80 - just omit this entirely.

 You may include a setting for user.opmlserver.folder that specifies a location other than the default, but the default should be fine.

3. After editing opmlStartupCommands.txt, quit the OPML Editor and re-launch. That should be it.

NOTES

 If your ISP blocks inbound requests on port 80, you'll need to setup the community server to run on a different port. I've got a tool to help you do this: it's about 95% complete. Check back if you need this tool.

Last modified: Friday, October 31, 2008 at 9:26 PM.
Contact
Click here to send a mail message to the author of this weblog.
January 2006
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
31
 
Dec   Feb
Subscribe:
Click here for the XML version of the information displayed on this page.
Weblog Commenting and Trackback by HaloScan.com