Here’s a (big) problem, if you want to install DF 1.6.10 on a local network (or intranet).
If you put DF on your local network and the internet connection goes down, the stack stops working all together, since it relies on assets located on other CDNs. While that could be a good idea to save resources, it has (at least) one big drawback: if there’s a problem with the connection to one of these CDNs (be it a problem on the backbone or simply a minor network problem) you can’t continue working. Also it’s impossible to use DF on a closed intranet.
IMO, there should be a fallback for any online-resource, so the stack can work locally as well, if the internet connection is down.
Hi Jason,
thanks for the quick reply and the good news! I was just about creating a bunch of vHosts to be able to work offline.
Do you think you could provide the .html until thursday evening? (I’m travelling over the weekend and it would be great to be able to work with DF when offline).
I’ll try that tonight and let you know what happened
BTW: Wouldn’t it be cool to put those links into a config JSON? So I could point these to the same files as in other components/applications on DF (and thus make sure no un-necessary files are loaded?)