import { get } from "lodash”;
@cianx There is an issue about it state/env sharing here, I'm linking the comment that could be of interest to you, but feel free to read the entire issue to get a bigger picture: https://github.com/webiny/webiny-js/issues/633#issuecomment-562548944
.env.json files are individual to every developer, we (at Webiny) do not push them to git.
If you have a certain way your company policy requires to handle/share .env files, that's totally ok, as we don't really force you to use them the way we do by default. All we care about is that certain ENV variables are present in process.env when we build/deploy.
So out of the box you get this setup with .env.json, but you don't have to use it if your needs are different.
.env.json files, it is unusable by other developers. There are not docs on where the .env.json files are required to be and there is a lot of pregenerated configuration content in those documents that and individual developer cloning the project would not know how to reproduce.
.env.json stored at the root. Which has the a few settings in it, MONGODB_SERVER and MONGODB_NAME, a developer could reasonably know. If I look at the .env.json in the both the api and app directories they contain a bunch of values I presume are generated by the serverless deploy. Which right now is a catch 22 as I cannot run the webiny deploy-api without .env.json files and I cannot create the .env.json files with out deploying the api.
I think it’s good you pointed this out. But if you take a look at those .env files, you can see there are just a couple of things you can configure, and the rest is populated by the CLI, once the stacks are deployed.
For example, in the api folder, you’ll have something like this in your example.env.json (coming in our upcoming release):
{
"default": {
"GRAPHQL_INTROSPECTION": true,
"GRAPHQL_PLAYGROUND": true,
"S3_BUCKET": "[BUCKET]",
"JWT_SECRET": "[JWT_SECRET]"
}
}Basically, all you have to enter here is the S3 BUCKET and the JTW_SECRET.
And if you open e.g. apps/admin, you’ll have something like:
{
"default": {
"SKIP_PREFLIGHT_CHECK": true,
"INLINE_RUNTIME_CHUNK": false,
"PUBLIC_URL": "/admin",
"PORT": "3001"
}
}These are React app settings basically.
The other entries, you might have for “local”, like you have in your sshot, are created by the CLI, once the API is deployed.
I understand that it might not be super-straight forward, and that we’ll have to improve on this. So in our next release, we’ll actually include some comments for new users, which will tell the user what every variable is about.
We’ll also have a separate article on how env variables work all together.
hi guys, today found your awesome project at git and would like to contribute dealing with some issues, but cannot install it locally. Local setup part is not working. Running webiny deploy api inside sample-project fails, webiny deploy-api produces an error, which I can fix renaming sample-project/webiny.root.js -> webiny.js. Running webiny deploy-api after produces
This is the first deploy of local environment, so it may take a few minutes.
Here's 🍎 to make the time pass faster :)
💡 Loaded local environment from /Users/mac/Work/Projects/webiny-js/sample-project/.env.json...
💡 Loaded local environment from /Users/mac/Work/Projects/webiny-js/sample-project/api/.env.json...
Error: Template file was not found! Make sure your serverless file has either ".yml" or ".yaml" extension.
at findFile (/usr/local/lib/node_modules/@webiny/cli/sls/template/serverless.js:29:11)
at Template.default (/usr/local/lib/node_modules/@webiny/cli/sls/template/serverless.js:47:26)
at async module.exports (/usr/local/lib/node_modules/@webiny/cli/sls/execute.js:33:20)
at async module.exports (/usr/local/lib/node_modules/@webiny/cli/sls/deploy.js:93:38)
at async Object.handler (/usr/local/lib/node_modules/@webiny/cli/cli.js:71:9)that's where I'm stuck. What can be done to address this one?
