Any way to avoid jsdelivr? #2185
-
|
So, apparently jsdelivr is blocked in Egypt for some reason I don't understand :( Right now whenever I try to add a smart cell like a chart or a database connection I get this error in the browser console
Which makes sense because I can't reach cdn.jsdelivr.net unless I use a VPN or something. My question is, Can I avoid jsdelivr at all? By bundling Vue differently and loading it from a local file for example? Or, Can the CDN urls or at least a base url be configurable somehow? .. cdn.jsdelivr.xyz seems to be working fine here (so far). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hey, perhaps it would help to get the .xyz IP with |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply, It works for me but I want to introduce Elixir to some non-technical coworkers, and livebook seems to be perfect for this because I can easily give them access to a copy of their real data (which they already understand) and let them play with it. I can manage to help them bypass blocking and DNS issues, but it's not sustainable .. and I don't want them to get the wrong impression that Elixir is hard to use just because of this. So I think when I have some time I can work on a PR to make this configurable instead, will something like this be accepted? ... And what do you think is a better/viable approach, configurable CDN or an option to bundle everything in build time? |
Beta Was this translation helpful? Give feedback.
-
|
Making the URL configurable is too much. I think we should just bundle, which we already do for |
Beta Was this translation helpful? Give feedback.
Making the URL configurable is too much. I think we should just bundle, which we already do for
Kino.DataTablefor example. I opened an issue to track that livebook-dev/kino#329.