4 ms·
(I’m one of the authors of Acha-Acha) Just to set expectations: * This is a project we’ve build for ClojureCup.com hackaton * We haven’t figured out how to d
by tonsky 12y ago
(I’m one of the authors of Acha-Acha)
Just to set expectations:
* This is a project we’ve build for ClojureCup.com hackaton
* We haven’t figured out how to do a proper hosted version yet and how to handle any real load. Please be patient as I occasionaly clean up/delete some repos so site remains responsible at least
* Some repos are too big or hang at some point so please accept I’ll drop them in that case. We’ll try to fix that but not in real-time
* There’s a self-hosted version you can use at your company internally (e.g. you want achievements but repos are private). Instructions are at https://github.com/someteam/acha https://github.com/someteam/acha
* Blog post about implementation details’ here http://tonsky.me/blog/acha-acha/ http://tonsky.me/blog/acha-acha/
* Some interesting highlights:
We use client-side DB (DataScript), all stated is downloaded to the browser, and all rendering happens without page reloads _and without API requests_ because all data is already there.
We use websockets for server push. So everything that happens on a server gets immediately pushed to the client. Including actions by other users, e.g. new repo added. No page refresh required.
And thanks for the warm feedback!