.mesh - to commit or not commit?

[mwasl]

Hey!
First off, really like this project and the features of it. It helps us bridge some gaps that were quite painful with apollo federation. Thank you for the hard work!

Problem

We are building our .mesh locally and committing it to git. What we noticed are constant re-orderings of imports and classes in the generated IntroSpectionSchema.ts, ./mesh/schema.graphql and ./mesh/index.ts files.
This is quite noisy from a development/ review perspective, we are quite often "scared" that some model broke, or something changed unintentionally.
We tried generating from URLs and from Source files, both without noise reduction.

Question

So i was wondering if it's common practice to commit the .mesh file?
Maybe everybody running mesh dev on production and we are the only ones that build and commit?
Could one do mesh build && mesh serve on container startup, or is this silly?
Or, is there a simple way to reduce the noise?
In general, I am mostly curious how others build the mesh without creating lots of noise in their commits.

Cheers,
Michael

[ardatan]

We don't recommend to commit .mesh or use mesh dev in production.
We don't guarantee the files inside .mesh won't cause random diffs.
You should run mesh build once then mesh start on the following runs.
The only scary point is to use mesh dev in production here :)

[mwasl]

What do you mean specifically by

You should run mesh build once then mesh start on the following runs.

In case you run the Mesh on Kubernetes in a container, what is the recommended way? Do you build in ci/cd and put everything in a container image, or do you execute mesh build and then mesh start when starting the container?

[ardatan]

No you need to run mesh build once while building the image then mesh start everytime you start the container just like any other build and run projects.

[mwasl]

I assumed so and it totally makes sense, wanted to recheck. Thanks for the quick answer!

[xmlking]

I am using this multi stage build.
https://github.com/xmlking/graphql-mesh-specific/blob/main/Dockerfile
not sure if I should copy tsconfig.json in runtime layer
Do I have to provide dotenv/config For mesh start like mesh build -r dotenv/config?

[ardatan]

Do I have to provide dotenv/config For mesh start like mesh build -r dotenv/config?

No

not sure if I should copy tsconfig.json in runtime layer

Copy the whole project