So I'm in the process of getting the latest version of discourse and realized (of course) that when talk.olab.io goes down, our feeds also go down. This is a good argument for a slightly more sophisticated caching / server side system on the olab.io side. It would give us the ability to pull more intelligently and make the olab.io site more responsive by pre-populating the quick-views.
Before too much work on this, we need a good architecture / design. I'm open to proposals :)
So I'm in the process of getting the latest version of discourse and realized (of course) that when talk.olab.io goes down, our feeds also go down. This is a good argument for a slightly more sophisticated caching / server side system on the olab.io side. It would give us the ability to pull more intelligently and make the olab.io site more responsive by pre-populating the quick-views.
Before too much work on this, we need a good architecture / design. I'm open to proposals :)