setup backups for #crisp clickhouse cluster

Release #crisp V4 in beta!!!

re-import all #crisp analytics data once again to clickhouse, after a change of schema to fix some duplicates

start import of 2.4 billion rows into clickhouse #crisp

import new #crisp analytics clickhouse data to production cluster and it's FAST

Back at work on #crisp, checking and merging last branches for V4

resume work on deployment the new #crisp analytics backend live, after morning coffee

finish setting up clickhouse cluster (3x data replicas + 3x "zoo"keeper nodes) for new #crisp analytics

continue reviewing #crisp analytics

work on replicating local #crisp analytics clickhouse into a cluster

Start reviewing new #crisp CRM profile view

continue reviewing new #crisp analytics based on clickhouse

Finish new helpdesk UI review and send all my feedback #crisp

start working on merging #crisp analytics v3 feature

Review new helpdesk UI #crisp

Continue reviewing MRs #crisp

re-create all kubernetes persistent volumes for #crisp enrichment api + #mirage databases, after finding out that they got created with a reclaim policy of delete instead of retain, putting the data at risk on the long term — TLDR if you use K8S always suffix the block storage class with -retain if your cloud provider supports it and if you don't want the data to disappear with a mistake

coffee late morning to chill down after intense 14 hours a day migration to kubernetes of #crisp service for the last 3 days

finish migrating #crisp enrichment api to k8s

almost finish moving #crisp enrichment api to k8s