Understanging ENV variables in PayloadCMS

KasparTr

last month

12

import { processGetAccountDetails } from './core/vault/controller';
console.log("server | ENVIRON: ", process.env.ENVIRON) // works
router.get('/vault/accounts', (req: any, res) => {
    processGetAccountDetails(req,res)
});

require('dotenv').config();
console.log("vault controller | ENVIRON: ", process.env.ENVIRON) // undefined

• 

  Teun

  last month

  Does this help:

  https://payloadcms.com/docs/admin/webpack#admin-environment-vars

  ?

• 

  KasparTr

  last month

  Like I said, I explicitly don't need them in admin panel. I need them in backend as I am using them (I have around 30). In some files they are undefined in production and I cannot find any pattern as to why.

• 

  thisisnotchris

  last month

  @KasparTr Are they defined in the same .env with your payload env vars?

  
  

  
  

  If that's the case, then it makes sense

• 

  KasparTr

  last month

  Yes, all in the same as payload secret var

• 

  thisisnotchris

  last month

  @KasparTr

  Payload will automatically supply any present env variables that are prefixed with PAYLOAD_PUBLIC_ directly to the Admin panel.

  
  

  
  

  However, it seems like you want to use them in the backend

  
  

  
  

  Maybe create an additional .env with your custom env vars

  
  

  
  

  and use dotenv to also include that

• 

  Jarrod

  Payload Team

  last month

  @KasparTr does this thread help you out?

  https://github.com/payloadcms/payload/issues/1654#issuecomment-1403972303
  

  
  

  I chatted back and forth with some others about this same topic in that discussion. Basically, you will need to add

  
  
  

  dotenv.config({
    path: path.resolve(__dirname, '../.env'),
  });

  
  

  atop your payload config file, and your server.ts file

• 

  KasparTr

  last month

  Yes this helps. For some reason, when I added the following to server.ts, things worked normally.

  
  
  

  import dotenv from 'dotenv';
  dotenv.config();