The Joyent Community

Hmm... so the dynamic DNS update like that could also be done for failovers.

Do you have fink? If fink is on your machine (you would have had to put it there) wget is a quicke install. And it's a good utility. Fink is too!

Fink is a package manager that simplifies installing a bunch of other littler things - it's not a utility like wget. I think if you want to install wget, the best way to do that is to use fink, but have you tried just changing the two wget's in the script into curls? I think they would both do the same thing, which is request a url which would then tell the server that your ip has changed and what it has changed too. Try it?

Well, I can now officially update my Dynamic IP with DNS Made Easy using a customized DME Update script. For someone new, I'll post the info below. This is for setting your dynamic IP address with DNS Made Easy on a Mac Panther.

-- Get wget and follow build instructions
-- Get DME Update script (there are others, but this one is more intentional and easy to add records)
-- Open config.pl from DME update:

        $cmd = "wget -O /proc/self/fd/1 -q \"$getip_ext_url\"";

-- change to:

        $cmd = "wget -O /dev/fd/1 -q \"$getip_ext_url\"";

-- and -- change from:

        # call the update servlet at DNS Made Easy
        $url = "http://www.dnsmadeeasy.com/servlet/updateip";
        $cmd = "wget -O /proc/self/fd/1 -q \"$url?username=$username&password=$password&id=$id&ip=$new_ip\"";

-- change to:

        # call the update servlet at DNS Made Easy
        $url = "https://www.dnsmadeeasy.com/servlet/updateip";
        $cmd = "wget -O /dev/fd/1 -q \"$url?username=$username&password=$password&id=$id&ip=$new_ip\"";

Well, I hope that helps somebody else. Not friendly stuff here. But we're not after your everyday localhost'n dev environment either.

Anyway, you might then check out CronniX to keep a cron job for updating your Dynamic IP with DME regularly.

Almost a side note after that, but now it's a matter of opening up a crack in the firewall to allow the new IP to point to the local Apache2 instance, rather than default Apache1 and "web sharing" stuff. But hey, that's only if I can get through sprint's dsl and an airport extreme. Didn't someone write a tutorial yet for "setup dynamic dns for localhosting on mac os x with sprint dsl and airport extreme with additional apache2 build while still keeping firewall on and security tight -- in a nutshell"? I'd almost pay for one.

Last edited by cameron (2005-01-22 07:25:04)

Okay, so "myip" from an external perspective is the IP of my dsl router. This is quite dangerous at the moment because there is a web-based dsl setup thingy available to the world. How do I get to the server itself?

Cameron, I don't use the SL packages, I built Apache2 and then sorta hammered on the instructions at the following link to make it work:

http://sean.typepad.com/ditto/2004/09/finks_apache2.html

Every time you bump the system you need to redo the process, I don't know if it's worth the effort or not. I suspect not.

cameron wrote:

Almost a side note after that, but now it's a matter of opening up a crack in the firewall to allow the new IP to point to the local Apache2 instance, rather than default Apache1 and "web sharing" stuff. But hey, that's only if I can get through sprint's dsl and an airport extreme. Didn't someone write a tutorial yet for "setup dynamic dns for localhosting on mac os x with sprint dsl and airport extreme with additional apache2 build while still keeping firewall on and security tight -- in a nutshell"? I'd almost pay for one.

I'm starting to wonder if this is even possible. Or worth it. The goal is to be able to test my dev sites with a win xp machine literally next to my mac dev machine. Without uploading to TextDrive first. Any other suggestions?

Damelon wrote:

I'm probably missing something, so I apologize in advance if that's the case, but testing what? The CSS? The XHTML? If that's what you are referring to by development, then uploading to a .textdriven.com domain is probably just as fast as the next thing. If you are talking about building something (say in RoR) then I'm not so sure testing it on XP is needed. All you would be doing then is serving the wrapping to XP which is again the XHTML and CSS, correct? The idea is simply to build it locally and check it's working before uploading it to a production server (in this instance probably TD), correct?

Maybe you're right. The planned dev environment, now that I've got more than myself developing sites, is keep everything in a repository, build most sites with TextPattern, custom plugins, always test locally first (we've seen here why this is important), then move to TextDrive for production.

You're right, though. I want to test with the windows machine mostly for xhtml and css. It's just nice to be able to test the layout and design as a full-on TextPattern site, with PHP5, custom plugins, etc. dynamically before uploading to TextDrive.

Working towards the future, it's ideal to have a development server for any sizable project. My thinking is to have my mac box be the dev server. But maybe I'm better off setting up a second FreeBSD machine? It could also be off-site (and outside my DSL router/network), but far away from TextDrive and it's shared environment.

Unless I can figure out how to allow access to my mac machine safely, I think I start looking for such a dev server.

edit: or until I can afford a dedicated server, right? :)

Last edited by cameron (2005-01-23 11:48:19)

Damelon wrote:

cameron wrote:

But maybe I'm better off setting up a second FreeBSD machine?

In my version of geek heaven, yes, I have a dedicated FreeBSD setup mirroring TD in total, just for giggles.

Yeah, what plan is that? :)

At this point I'll settle for being able to test on IE win xp with it directly plugged in to my mac. And it works fine once personal web sharing is turned on. But for anyone trying this with a non-apple apache build on their mac, I could only get this to work with the help of the link D posted above. Email me if you need help with it.

Thanks kemmott -
I didn't need to mess with anything on the windoze side once the mac's web sharing was (tricked) on (thanks Damelon). Can visit www.siteone.dev or localhost of my mac apache2 dev server.

It's working rather nicely -- and sites are less of a crap shoot now with my windoze based clients. :)