Home servers, anyone?

[Jerry Jensen]

I just pick it out of a shell(“ifconfig”). I have something running all the time on that machine - its taking data and sending it to me also on dropbox. A cron-ish job could do it just as easily.

> On Oct 27, 2015, at 8:12 PM, Roger Eller <roger.e.eller at sealedair.com> wrote:
> 
> I almost suggested phx_dropboxlib for that (just to keep it in LiveCode).

> On Oct 27, 2015 11:05 PM, "Jerry Jensen" <jhj at jhj.com> wrote:
> 
>> I’m doing a similar thing, but writing the current IP# to a particular
>> dropbox file that is shared with me.
>> 
>>> On Oct 27, 2015, at 1:39 PM, Roger Eller <roger.e.eller at sealedair.com>
>> wrote:
>>> 
>>> I know someone that had a dynamic setup like you describe.  It was simple
>>> and easy for 1 person access.
>>> 
>>> He had a local script checking the IP every 5 or 10 minutes (at home).
>>> When it no longer matched the last known IP, the script would write a
>> small
>>> text file TO A WEB SERVER that was hosting a site he owns.  Then from
>>> anywhere, he could access that file to find his way back home (so to
>> speak).
>>> 
>>> ~Roger
>>> 
>>> 
>>> On Tue, Oct 27, 2015 at 3:45 PM, Richard Gaskin <
>> ambassador at fourthworld.com>
>>> wrote:
>>> 
>>>> Most of my servers have fixed IP addresses, but I'm about to add one to
>> my
>>>> home where the IP will be dynamic.
>>>> 
>>>> The most common solution for making servers with dynamic IPs findable is
>>>> DDNS, and there are of course many free providers of such a service.
>>>> 
>>>> Put since this isn't a public server (just for testing and
>>>> experimentation) I'll be the only user, and it occurs to me I could
>> take a
>>>> few minutes to craft a simple solution to know the server's current IP
>> by
>>>> using a CGI at one of my sites hosted with real DNS in conjunction with
>> an
>>>> auto-run app on the server to call it similar to what many DDNS services
>>>> use.
>>>> 
>>>> I'm inclined to do that only because I like tinkering, but I thought I'd
>>>> check in here to see if this very specific use case was something others
>>>> might have a need for.  If so, I might get around to documenting the CGI
>>>> and sharing it, but since most folks just use DDNS I'd guess this
>> 302-based
>>>> workaround is probably too use-case specific to be of interest.  If I'm
>>>> wrong let me know and that'll motivate me to get around to documenting
>> it
>>>> that much sooner.
>>>> 
>>>> --
>>>> Richard Gaskin
>>>> Fourth World Systems
>>>> Software Design and Development for the Desktop, Mobile, and the Web
>>>> ____________________________________________________________________
>>>> Ambassador at FourthWorld.com                http://www.FourthWorld.com
>>>> 
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode