Replies: 3 comments 18 replies
-
@cipami have you managed to make it work ? |
Beta Was this translation helpful? Give feedback.
-
Hi. Please consider linked example for Next.js assumes the env variables will get bundled during build process. You can do the same by passing build time runtime config. I highly recommend using platform native Environment Variables for dynamic environment config (otherwise, you essentially need to commit a new Docs: https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html |
Beta Was this translation helpful? Give feedback.
-
Has anyone got the server environment variables to work? I can get them on my client using the public runtimeConfig in my nuxt.config.js, but the server environment variables are always undefined, whether calling them from process.env or using the runtime config. I've used the build commands to inject them into .env and .env.production, but both have the same result. |
Beta Was this translation helpful? Give feedback.
-
Anyone managed to inject .env to Node runtime on AWS Amplify?
Only docs about it I found is this: https://docs.aws.amazon.com/en_us/amplify/latest/userguide/ssr-environment-variables.html which doesn't work as Nuxt does not auto load .env files on prod.
Beta Was this translation helpful? Give feedback.
All reactions