I understand.

But still, is it possible to debug the open-source repos? At least we can try it freely and give more feedback.

Hi guys, this product looks great ! But i have the same problem as loicsaintroch, with 'estraverse-fb'

Hey loicsaintroch 🙂 Our backend contains two parts. The first part is the api layer that is responsible for generating the graphql schema from the internal representation, creating the correct mutations, performing validation etc. This part is open source. For the api layer to be useful though it requires you to plug in a backend that is responsible for fulfilling requests from the api layer, such as querying and creating data. We have a multi tenant implementation of the backend that we use in production, but unfortunately it is too coupled to our infrastructure to simply open source. We are in the process of refactoring the entire thing, which will enable us to provide a version of the backend you can host yourself. It’s a fairly big task and we don’t have an eta yet.

@sorenbs: All right thank you for the details. So if I understand correctly, the stack will be completely open-source in the next few weeks/months?

We will continue to have an internal multi-tenant implementation of the backend, but we want to provide a simple implementation of the backend that you can host on your own.

Sounds great! 🙂

We simply didn’t have time to work on it yet and until now we have seen an overwhelming demand for new features in the hosted version, so that is where we have been spending our time. Really looking forward to get the open source implementation ready though!

Yes I understand. Please let me know when you fixed the open-source version though, I’d love to contribute.

That would be amazing! I’ll reach out to you when we are ready for it.

@sorenbs: When do you think you’ll be ready for it?

this looks really promising, i would love to try the self-hosted version and contribute too

The only thing I can get working is by installing the version from npm … But then it crashes on a request and the dashboard still doesn’t work.

@loicsaintroch: we’ll let you know as soon as our new backend infrastructure is ready for being open sourced. However we won’t use NodeJS anymore since it’s no longer the right fit for us.

Hey! I finally got the open-source API and dashboard built. The API is running. But impossible to start the dashboard properly because I have this error in the API :

PersonSortBy values must be an object with value names as keys.

How can I fix this?

Can you share the query that generates this error?

Way cool that you are hacking away on this btw 🙂

No query in particular. I just made the API up and running, but as soon as I start the dashboard connected to the API the dashboard can’t display anything because the API returns this error.

Could you copy the exact request from the network tab in chrome dev tools?

(I run the API thanks to your example in https://github.com/graphcool/api/tree/master/examples/books)

The body contains the query

I’m afraid that example might be horribly out of date...

I can’t run the dashboard properly because it can’t access the API correctly probably because the example doesn’t work

So … kinda messy

I have this config in my dashboard :

"react-relay-schema": "<http://localhost:60000/schemas>”

And the default route you give in the example without

.json

You could try to isolate it a bit by running the dashboard against the production api

it’s already in a production env

When you have verified that the dashboard is running correctly you could return to the backend.

Not working….