3 ms·
Do you have a way to turn off your automatic telemetry? It seems like one of the first things the UI does is send a bunch of info back to Sentry. It also appea
by Aeolun 4y ago
Do you have a way to turn off your automatic telemetry? It seems like one of the first things the UI does is send a bunch of info back to Sentry.
It also appears that the email verification works by passing the email straight on to one of your servers, instead of my own SMTP setup, which is promptly blocked by my spamfilter.
EDIT: Limit on the password of 20 characters? It's hashed anyway right, who cares?
More Edit: I'm trying to add a data source, and even though I'm self-hosting it's displaying:
> Credentials will be encrypted & stored securely on our servers. Connect Type Cloud: ILLA servers will securely connect to your database.
I'm going to stop testing now, since I have no desire for my database credentials to be floating around on your cloud like my email already is.
- vicsomething 4y ago
- deleted 4y ago[deleted]
- smallSohoSolo 4y agoHey Aeolun, thank you for your testing! This is the co-founder of ILLA. The automatic telemetry issue was caused by not deploying ILLA builder from CLI. For the email verification issue, we will support customized SMTP very soon to ensure our users have 100% control of their data. We will change our password limitation to 30 characters so that our users will have more flexibility. The most important thing is that showing the message"Credentials will be encrypted & stored securely on our servers. Connect Type Cloud: ILLA servers will securely connect to your database" is a bug. If you deploy it locally, your data will not transfer to our server. We will fix it asap and update a version tmr. I will keep you updated once we have the bug fixed.
- swznd 4y agowhat the purpose of limiting the password characters anyway ?
- vicsomething 4y agoHey Aeolun: illa-builder@1.3.6 is here! NEW: · Add sentry address configuration. Sentry will only start with the configuration. Improvements: 1. No longer limit the length of the password 2. Stop pushing the misleading message when the users create new resources during self-hosting 3. Routing optimization. There will be no more infinite loop 4. WebSocket improvement