I am also agree that is is not a good solution since the user can delete
it by error by cleaning homepage dir.
The two options look good, perhaps the first option is more direct for
the person which construct the demo ?
Le 25/02/2014 12:49, Miguel Colom a écrit :
Quoting Bertrand Kerautret <[email protected]>:
Yes, but it is just an image tools exploited in the script for
instance here:
https://github.com/nilx/ipol_demo/blob/master/app/40/template/params.html#L140
And sorry it doesn't mention purple but just http://dev.ipol.im/~x
I use it for the demo 71 (http://dev.ipol.im/~kerautre/ipol_demo/71/)
To limit the pb I can use le same link than the actual demo 71.
Thank,
Bertrand
Well, the URLs in http://dev.ipol.im/~xxx belong to the Purple server,
so it's the same problem.
In my opinion, this particular demo is doing wrong hotlinking the image
from Purple, and this should be always avoided. The behaviour of the
production server should never depend on the test server.
I'd recommend that all demos don't use any static content
(scripts/images) and follow the standard structure. If this isn't
possible, then we have to think where to put them.
We have two options:
1) Add static directories to the demos.
2) Create a central repository of static content where all demos can
hotlink any script or image they need.
Miguel
--
IPOL - Image Processing On Line - http://ipol.im/
contact [email protected] - http://www.ipol.im/meta/contact/
news+feeds twitter @IPOL_journal - http://www.ipol.im/meta/feeds/
announces [email protected] - http://tools.ipol.im/mm/announce/
discussions [email protected] - http://tools.ipol.im/mm/discuss/
--
IPOL - Image Processing On Line - http://ipol.im/
contact [email protected] - http://www.ipol.im/meta/contact/
news+feeds twitter @IPOL_journal - http://www.ipol.im/meta/feeds/
announces [email protected] - http://tools.ipol.im/mm/announce/
discussions [email protected] - http://tools.ipol.im/mm/discuss/
