process-analytics / bpmn-visualization-js

A TypeScript library for visualizing process execution data on BPMN diagrams
https://process-analytics.github.io/bpmn-visualization-js/
Apache License 2.0
216 stars 29 forks source link

[INFRA] move demo and examples to the new statically.io Staticzap service #776

Closed tbouffard closed 3 years ago

tbouffard commented 3 years ago

"Statically Sites has been deprecated, if you are still using this service, you can use Staticzap as an alternative."

tbouffard commented 3 years ago

We aren't using "Statically sites". This service was designed to serve through the statically.io CDN resources usually available from a given domain. For instance https://cdn.statically.io/sites/<domain_name>/path/to/image.jpg. The service will be replaced by url like https://cdn.statically.io/js/example.com/script.js or https://cdn.statically.io/css/example.com/style.css. See https://statically.discourse.group/t/statically-api-key-in-cdn-url/99

We already use the staticzap service for the GitHub integration, the service has just been renamed recently. Urls are unchanged, examples are still available at https://cdn.statically.io/gh/process-analytics/bpmn-visualization-examples/master/examples/index.html

However, the CDN cache policies have changed, see https://statically.io/docs/using-staticzap/ In particular, we cannot use PR branch of the examples repository in url has the resources are cached once for 1 year. We now must use commit if we want to see latest changes. Be aware that for resources from the master branch, all files will be cached on the CDN for 1 day, so changes don't immediately show up any more.

csouchet commented 3 years ago

Shouldn't this issue be created on the repo bpmn-visualization-examples rather than this one? Because we don't use 'statically' for the library.

tbouffard commented 3 years ago

Whatever where this issue is, we reference statically.io in the README and in the documentation. I thought it was easier to remind this issue here as we are daily working in this repository And we are going to close the issue with a wontfix, this is clearly not a problem IMHO