Prisma

Screen Shot 2018-08-29 at 3.25.09 PM.png

I want to ask. what's the usage of app project? how can I change local graphql port

the port is set in the config object that’s passed to the `start` method of `GraphQLServer`:

```
const options = {
  port: 8000,
}

server.start(options, ({ port }) =&gt;
  console.log(
    `Server started, listening on port ${port} for incoming requests.`,
  ),
)
```

you can find some docs here: <https://github.com/prisma/graphql-yoga#startoptions-options-callback-options-options--void----null-promisevoid>

:ok_hand:, so the app project is useless now?

nope, the `.graphqlconfig` is important for tools like the GraphQL Playground or the GraphQL CLI. For example, if you want the Playground to show both projects side-by-side, you need to have a `.graphqlconfig` file that specifies both

How can I see the app project in Playground?

Screen Shot 2018-08-29 at 4.04.53 PM.png

In my demo, I can see the usage of database project.

when you’re running the `graphql playground` command it should show you a sidenav with trhe `app` and `database` projects

check the end of this page for a bit more context: <https://www.howtographql.com/graphql-js/5-connecting-server-and-database/>

Screen Shot 2018-08-29 at 4.10.53 PM.png

Is there any relation between GraphqlServer and .graphqlconfig.yml file? Can this server use the app project?

&gt; Can this server use the app project?

Hmm not quite sure what you mean by this, the `GraphQLServer` basically _is_ the `app` project.

`.graphlconfig` is “just” a way to provide information about your GraphQL server to the GraphQL CLI and the GraphQL Playground. You don’t _need_ it but it simplifies certain worfklows.