Explicitly mention that developer should create a new `.env.server` file, and not use `.env.server.example`

[matijaSos]

Is that the idea, did I get it right? I got across this at https://docs.opensaas.sh/guides/authentication/#google-auth, where it is mentioned to add stuff to .env.server file, but we never created it in the first place. So I wasn't sure if I should create a new one, reuse the example one or sth else. Would be nice to have some tip about this.

[GavPierce]

I believe it is mentioned in the Docs -> Getting started:

[vincanger]

yep! thanks @GavPierce 🙏

is that enough @matijaSos or do you think the instructions could be improved somehow?

[Martinsos]

What I did in wasp new is actually added a command to do it:

cp .env.server.example .env.server

I would consider doing that. I know for me, when reading docs, most of my focus goes on code to copy and execute :D, and less on text, and this way you make it really easy for me to do the right thing. I would keep the text, and just add this after it.

Oh and this can be mv if you want, but I actually liked copying better, because it is useful to have .env.server.example there if another teammate checks out the project. Yeah, I would advise copying, not moving.

[vincanger]

cool. I will add this to the docs now @Martinsos!

I think i'll close this issue for now then as it seems we've covered it.