4 ms·
Looks promising. There are a couple of things that worries me though. (I haven't tried it yet, only skimmed the docs) 1. Telemetry needs to be opt-in during in
by vichle 4y ago
Looks promising. There are a couple of things that worries me though. (I haven't tried it yet, only skimmed the docs)
1. Telemetry needs to be opt-in during install.
2. The roles are weird, why would a developer need write access by default? That's just a recipe for disaster. Would be better to default to read-only in all roles and allow upgrading to write permission as an active choice.
3. There needs to be a clear way to distinguish between prod/staging. I like clients where you can change the background color for different connections, eg screaming red for prod.
Good luck, keep up the good work
- paraswaykole 4y agoThanks for the awesome suggestions. On point 2, I had removed the roles part from the software code, since it was absurd at the moment. Just need to update the same in docs.
- mmaia 4y ago+1 on the opt-in telemetry
- paraswaykole 4y agoagreed. will make it opt-in telemetry.
- db3pt0 4y agoNot only should telemetry be optional, but a failure to send it should not result in the application refusing to run¹. With a host-level block of PostHog, the server crashes with: Post "https://app.posthog.com/capture/ https://app.posthog.com/capture/": dial tcp x.x.x.x:443: connect: connection refused 1: https://github.com/slashbaseide/slashbase/blob/a7cb7871b07a978009b649ccc55f0858e1325188/internal/tasks/cron.go#L42-L47 https://github.com/slashbaseide/slashbase/blob/a7cb7871b07a9...
- paraswaykole 4y agothanks for pointing out. will be fixed.