Automerge partykit integration

[shadrach-tayo]

Description of the Problem / Feature

• Scale automerge sync server with Partykit and cloudflare workers

Explanation of the solution

• Disable WebSocket Sync server used with Automerge repo in Desci-repo project
• Implement Custom Partykit WebSocket client Adapter and Postgres Storage adapter that integrates well with Automerge repo and cloudflare sync server.
• Setup local cloudflare (wrangler/workered) deployment with docker/docker compose for local development setup
• Add Github actions for deployment of cloudflare workers on staging and production
• Setup/deploy hyperdrive database tunnel and test

Todo checklist

• Integrate party module into local dev setup
• Setup party module k8s deployment for staging and prod
• Integrate partySocket in desci repo (manage connections properly) or connect through desci-server

Pre-deployment merge todos

• Update kubernetes Vault with new cloudflare websocket server routes (PARTY_SERVER_URL)
• Add cloudflare Api token secret to k8s vault (PARTY_SERVER_TOKEN)
• Set API_TOKEN value on deployed worker secrets and redeploy
• Set ENABLE_PARTYKIT_FEATURE=0 on staging and prod vault, after deployment of cloudflare workers, update env to flag to 1

[shadrach-tayo]

stale