Solved thread

This post is marked as solved. If you think the information contained on this thread must be part of the official documentation, please contribute submitting a pull request to its repository.

The Phalcon Debug reaches out to cloudfront.net?

I see that the Phalcon Debug error output display reaches out to cloudfront.net. I find this to be poor taste.

Am I the only one out there who doesn't always program while on a Internet connection and also feels like allowing external javascript to run in my development environment is a bad idea? Perhaps the default color scheme could be changed to make it readable without the prettify code being run? As it is it is greyed out to the point that it is not readable when the JS plugin is not run.

Additionally since I'm at it I'll say that there doesn't appear to be any offline Phalcon documentation. It works well enough to do a Firefox save webpage complete for each section but it seems that this should be more easily available.



6.4k
Accepted
answer

I can't speak for certain but it looks to be an easy way for it to include its assets regardless of the project setup.

You can look at the URI and check its includes if you feel unsafe: http://d2yyr506dy8ck0.cloudfront.net/debug/1.2.0/

Obviously the real answer is dont use it. Using step debugging with xdebug is infintely more powerful

Also offline documentation... a simple google search answers that question: https://www.google.com/search?q=phalcon+offline+documentation&pws=0&gws%5rd=ssl



84.5k

Static js/css resources are large and cannot be included in the extension itself. So we're using a CDN, you can download those resoruces and serve them from localhost.