But because of the way that some webapps are written, they require an absolute url (rather than a relative one) to refer to pages internally.
One easy workaround that I forgot to mention (possibly the easiest of them all) when I posted before is to set the IP as the domain name! So just rerun the init script (path bottom of my first post) and just use the desired IP when it asks for it. I have used this with other TurnKey webapps that require a domain name and it's worked, but I haven't tested with Zurmo (I have no reason to think that it won't work though...)
Another way to go would be to use a Dynamic DNS service. AFAIK TurnKey's own HubDNS should even work with a LAN IP (e.g. 192.168.x.x/10.x.x.x/etc). Other DynDNS providers may also allow that too but YMMV...
In essence you are right re DNS
But because of the way that some webapps are written, they require an absolute url (rather than a relative one) to refer to pages internally.
One easy workaround that I forgot to mention (possibly the easiest of them all) when I posted before is to set the IP as the domain name! So just rerun the init script (path bottom of my first post) and just use the desired IP when it asks for it. I have used this with other TurnKey webapps that require a domain name and it's worked, but I haven't tested with Zurmo (I have no reason to think that it won't work though...)
Another way to go would be to use a Dynamic DNS service. AFAIK TurnKey's own HubDNS should even work with a LAN IP (e.g. 192.168.x.x/10.x.x.x/etc). Other DynDNS providers may also allow that too but YMMV...