Ian Webster

Hi @flash1293, chart evaluation is subject to the limitations of NodeVM and should only be open to trusted parties. This is noted in the [readme](https://github.com/typpo/quickchart#securing-your-self-hosted-instance): > If you are hosting...

Thank you Siriwat. I've had problems with using Chartjs globals in the past because the settings would leak and affect other chart renders. I think that may be a problem...

Sorry, I misunderstood. I was imagining and option that allows you to set font color. That could cause problems because the Chart object persists between requests. However, you've implemented this...

This is a great idea. I already have most of the URL shortening infrastructure because QuickChart has a shorturl option for the chart rendering service. I'll look into providing this...

Hi @pooyaostvoar, the word cloud endpoint is not currently part of the Docker image. Perhaps in a future release..

This is an issue introduced by node-canvas 2.7.0. Specifically, array values for fillStyle stopped being supported because it is non-standard according to the canvas spec: https://github.com/Automattic/node-canvas/commit/4ce04af854da7b63b0ad84a0abd030f95846e55d https://github.com/Automattic/node-canvas/commit/bf5126b3847a02a9ea80febba22aefba88c97ee2 Unfortunately for us,...

Hi @sspread, access to the chart context is limited in the Community version of QuickChart due to more CPU-intensive sandboxing requirements. You can access the chart context by using the...

Can you show me an example? I can suggest an alternative.

This feature is tricky because I am wary of encouraging custom Javascript (which places stress on the free servers), plus the helper functions need to be specified outside of the...

Your environment on Cloud Foundry is missing dependencies, specifically puppeteer dependencies. You can learn more about dependency troubleshooting in the puppeteer docs: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md Hope this helps!