Thanks for the transition to gopherjs for the publisher. I asked Googler @cetico <https://twitter.com/cetico>with side project http://stardew.farm/ why reactjs over goherjs at the Full Stack Go meetup June 23 http://www.meetup.com/golang/events/231455969/
100% server side rendering ~ bad UX. Gopherjs great base ~ frame work missing features. JS dev joined the project ~ who knew reactjs. Splitting out the publisher from UX seems like the best way to "tree shake" at this time (is my research). Full recording https://youtu.be/liL20kmhcwo On Wed, Jul 20, 2016 at 10:15 AM, Mathieu Lonjaret < [email protected]> wrote: > Hi, > > just a heads up, for anyone using the publisher in production. > > As we're transitioning the publisher so it does more on the > client-side (browser) with gopherjs, I overlooked some authentication > aspect, and so the recent changes with it won't work out of the > localhost context. > So until that's fixed (I'll say when), you should stay below commit > faac33f4097e1ff3f6cb4fe661525df69304d497 if you still want the > publisher to work. > > Apologies, > Mathieu > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
