Prisma

For 1.0 is going self-hosted with docker the way to go currently?

we'll release more exciting news here soon :slightly_smiling_face: stay tuned!

same thing about the docs, several JS error inside the console and the menu not working

fixed, thanks <@U8LPYUCPJ> <@U7RFZM24C> :pray:

Yes openen 1.0 docs does not work with js

<@U0RQY0KK5>Thanks! It's running for me again! By the way, I've been having performance issues for some time. Some of the requests are resolved almost instantly (less than 200ms), but some of them gets stuck, and I have to wait even 5-10 seconds. Do you have some lower priority que for projects with free plans? Or why is this happening?

Hohai people, it seems like the GraphQL Playground’s latest update (standalone version on macOS HS) is crashing really often

Unfortunately no.. The UI gets completely white sometimes

Yes; deployments to the shared cluster are subject to volatile response times :slightly_smiling_face:

Please reach out to `support@graph.cool` if you have further questions about this topic :slightly_smiling_face:

<@U0RQY0KK5> so are the 502/504s expected to be resolved now? :slightly_smiling_face: thanks!

Hey <@U0RQY0KK5> - 1.0 `public-shared` is down probably the same thing you were all referencing 2 hours ago??

I think it was normal 0.x clusters before

But I think they're rolling out an update rn

Thanks. So just sit tight?  Or is there some config I can change

nope, don't think so, it just tells me that the cli version is outdated

<@U0RQY0KK5> Had a perfectly working function and havent deployed recently -- randomly stopped working last night. Any particular reason?

Is there a fancy way to generate documentation from code for API in graphcool@beta in form of html?

Just tried deploying to my staging service and got `ERROR: No service with id 'cj9ywlvq9edmz0198wix46dl0'` - anyone else seeing services disappear?

I'm just hitting the same problem. What version of graphcool are you deploying with?

<@U7Y29TG8L> Are you still seeing this issue? I am

Function view in the web console is not loading...is that a known issue?

```system:1 POST <https://api.graph.cool/system> 504 (Gateway Time-out)```

```Failed to load <https://api.graph.cool/system>: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '<https://console.graph.cool>' is therefore not allowed access. The response had HTTP status code 504. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.```

It takes an insanely long amount of time for it to load for me.

Hi all what's the step by step online deploying with vue.js, apollo, and graphcool
1st is install node, docker, and graphcool on server ?

I'm trying to use `graphcool-framework export` to get a copy of my data, but I'm realizing my command is just `graphcool` where am I going wrong? my service is not a legacy project, but I'm not on graphcool@beta. is it just that my cli has fallen out of date? I think my version of the graphcool cli is 0.10.1

graphcool/0.10.1 (darwin-x64) node-v6.10.3

will this update the one I have or is it separate?

ah. why two? is mine the legacy one? or do they each have reasons to be?

right, but will I start using `graphcool-framework` for everything? or will I still need to use both for different purposes?

please read <https://github.com/graphcool/graphcool/releases/tag/0.11.4>

Screenshot 2018-01-09 13.54.41_preview.png

<@U0RQY0KK5> `this example` link is broken from the ‘Service Definition’ docs: <https://www.graph.cool/docs/reference/service-definition/graphcool.yml-foatho8aip>

here is the page it leads you to: <https://github.com/graphcool/graphcool/tree/master/examples/permissions>

Hey everyone <!here>, a while ago we started the developer preview for Graphcool 1.0.
Now, we're super excited to announce *the first release candidate of Graphcool 1.0*, where we've integrated all the great feedback we've received so far.

Go check it out here: <https://blog.graph.cool/graphcool-1-0-release-candidate-7bc575f60d0e>

Rock on :rocket:

Thanks for all the hard work getting to RC1 <@U0RQY0KK5> and team!

You’re building something of great elegance here!!