Clojurians Log v2
clojureverse-ops
Purely fyi: More 504 errors at https://clojurians-log.clojureverse.org/fulcro/2018-03-29. Thank you, all! (Hi, @mitesh! 🙂
Site is back up now!
@mitesh Just an idea — I had suggested this to @plexus many moon ago. Given the frequencies of these errors: Have you ever thought about turning the entire Clojurians Slack Archive into a static site? Upon any new data, render the new day, or re-render days affected. (If you go down this route, we could eliminate the need for a bunch of infrastructure required for some of our own Slack archivers for ITREV, including Ngnix, etc.)
Hey Gene! That's a great idea and I've thought about it a lot! I'm working on a v2 of clojurians-log and going to spend a lot of time building it after next week (one of my plans for the holidays) 😁 I've written up some of my thoughts of why I don't want to do static site rendering even though I love static sites in the README: https://github.com/oxalorg/clojurians-log-v2
Nice! I love the way you thought this through — how’s life going back to Postgres, instead of Datomic? 🙂 Thx for helping keep Clojurians Slack archive running — it’s so valuable!!!
Hehe thanks! 🙌 I think the slack schema fits quite well in the relational model so I'm not feeling the pain (yet..) 😁
Or if the problems stem from Datomic, are memory related, and not well understood, have you reached out to the Datomic team for help? Given how generous you folks have been with creating this service for the Clojure community, the Datomic/Clojure core team might be happy to help.