ljplicease: (pensive)

I am looking for a web based Jabber/XMPP client application to sit on my web server. The jabber server itself is on the same physical machine, although it is a different IP address. Ajax is okay, but all data between the web browser and the web server would have to be over port 80 or 443 (https), so that it won't get blocked by people trying to access it at work. Ideally something easy to integrate with apache (a PHP application for example), but I'd also consider a mod_perl or Java servlet if it came down to that. Any one have any recomendations? Google search suggests a number of options, but I am not sure which would be best.

ljplicease: (Apple)

So I have just done away with the legacy dependency on Apache 1.3.x for nullray, and freed up the IP address that it was using (64.38.18.198). I was sort of looking forward to freeing up the IP address, but now that I have it, I'm not sure what I want to do with it. Ideas?

ljplicease: (Rust)
I came by this T-Shirt on the Internet today:

http://www.bustedtees.com/product.php?name=dysentery

which probably doesn't mean much to you if you didn't go through the American education system in the late 80s early 90s like Tyler and I did, but we both found it hilarious. I then proceeded to download the latest version of The Oregon Trail, which they are still apparently making, but of course the new version left something to be desired, namely the nostalgia, which only the original could provide. This is really the only thing that it has going for it.

I've been mucking about with nameservers... I was still using belmont as my DNS server, and I'm only now starting to do the switchover to nullray (DNS is/was the last service on belmont). Some of my websites may be temporarily mucked up. I will be doing nullray soon. For those of you who logon, you may want to remember that the IP address is 64.38.18.2 or add it to your hosts file. Shouldn't need it, but just in case.
ljplicease: (pixel2)
I told Chuck that I was moving a couple of months ago. We agreed that nothing had to change, that I could do my job running the server as easily from down under as anywhere. I was nervous that he'd freak that I was leaving, but when he didn't it was one less thing that I had to worry about in the move. Then New Year's day I get this phone call from him and an e-mail telling me, more than asking, that the server billing needs to be transferred him, and that I need to show Jay how to do the few several tasks which are required to be done manually. Apparently he sent me a snail mail asking about it just before I went to Salt Lake for Christmas, but I never got it. I felt blindsided by this whole thing.

Anyway, I suppose I should have expected it. When I originally started the account with RackSpace (who have been wonderful, btw-), Chuck would insist that he get the bill and I'd say, "but that is not what we agreed to." Then a couple of weeks later he'd be back at it. It died down for a while. It hadn't come up for years.

So I've decided to get my own server. Everyone with belmont accounts (there are like four of you out there) will get an account on the new machine instead: nullray. The downside is that I have to configure the system to support all of the services that belmont currently takes care of. The upside to this thing is that the new machine will be much faster (2.4GHz), have more memory (1GB), larger hard drives (2x160GB) and newer operating system (Fedora 4).

For those of you with email or shell accounts I will let you know more when there is more to know. I expect the transition to be largely transparent, but you will at least have to remember to ssh nullray instead of ssh belmont during the switchover.

Profile

ljplicease: (Default)
ljplicease

April 2017

S M T W T F S
      1
23 45678
9101112131415
16171819202122
23242526272829
30      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 23rd, 2026 02:38 pm
Powered by Dreamwidth Studios