Env vars client side prod server

eddiedev2 years ago

6

• 

  notchr2 years ago

  @956312590793977957

  One option is extending the exposed webpack configuration

  
  
  

  And using the webpack env variable plugin

  
  
  

  May work with YAML config?

• 

  eddiedev2 years ago

  hey

  @1049775120559898725

  something like this?

  
  // customAdminBuild.js const path = require('path'); // Tell Payload where to find your Payload config - can do it either here, or in package.json script process.env.PAYLOAD_CONFIG_PATH = path.resolve(__dirname, 'src/payload.config.ts'); const { build } = require('payload/dist/bin/build'); const buildPayloadAdmin = async () => { // Fetch your environment variables here // And then run

  build

  build(); } buildPayloadAdmin();
• 

  notchr2 years ago

  hmmm

  
  
  

  It's worth a shot! I'm not super familiar with yaml

• 

  eddiedev2 years ago

  unfortunately, after some research, this wont work since we cant add env variables during the build. It is added after the build. 😦

• 

  notchr2 years ago

  @956312590793977957

  but surely you can import the vars right?

• 

  eddiedev2 years ago

  hey

  @1049775120559898725

  . I couldn't apply the above since we build first and add env vars later. I Tried various things and came up with a solution. What I landed on was setting up a route to the backend to get the payload_public env var that I needed, then persisted the data using localStorage in the frontend. Not ideal, but it will do.