I have gotten it implemented however the issue remains that the default logging of parse still creates a log dir

var ParseServer = require('parse-server').ParseServer
var logger = require('parse-server').logger

// Imports the Google Cloud client library for Winston
const {LoggingWinston} = require('@google-cloud/logging-winston');

logger.options = {
    logsFolder: null,
    jsonLogs: false,
    verbose: false,
    silent: undefined
}

logger.adapter.addTransport( new LoggingWinston({
    projectId: parseConfig.gcpProjectId,
    credentials: {
        client_email: serviceAccount.client_email,
        private_key: serviceAccount.private_key
    },    
  }));

  
  try {
    logger.error('warp nacelles offline '+ env);
    logger.info('shields at 99%'+ env);      
  } catch (error) {
      console.log(error)
  }

This is causing issues in my GAE environment as writing directories is not allowed, I have also specified in logsFolder: null, in my parse init

Other related issues and approaches I have tried

#2855
#2518
#6205
#391

Strange behaviour, even when specifying an alternative logs directory name (other than null) parse still creates a logs folder as well as the other custom folder

After some source code review Ive found a work around by setting process.env.PARSE_SERVER_LOGS_FOLDER=null

Seems ./src/Options/index.ts maybe should have the type logsFolder: string | null ? Im not sure about the internals of parse or what to tweak or id submit a PR but I think it can be corrected in this block in ./src/defaults.js

const { ParseServerOptions } = require('./Options/Definitions');
const logsFolder = (() => {
  let folder = './logs/';
  if (typeof process !== 'undefined' && process.env.TESTING === '1') {
    folder = './test_logs/';
  }
  if (process.env.PARSE_SERVER_LOGS_FOLDER) {
    folder = nullParser(process.env.PARSE_SERVER_LOGS_FOLDER);
  }
  return folder;
})(); 

+1
I'm setting logsFolder to null but the Log folder and empty files each day are still created.

I'm using the following configuration:

const api = new ParseServer({
  databaseURI: mongoDSN, 
  cloud: './cloud/main.js', 
  allowClientClassCreation: false,
  appId,
  masterKey, 
  logsFolder: null,
  verbose: false,
  silent: false,
  ...

Parse Server version: 3.10.0

Have you tried with process.env.PARSE_SERVER_LOGS_FOLDER=null like @REPTILEHAUS suggested?

Hi @davimacedo ! If I set process.env.PARSE_SERVER_LOGS_FOLDER=null logs folder It's not being created but I think that conf object passed to ParseServer instance should be taken into account in order to config log folder too.

Thanks

Got it. This is something that can be really improved. Do you want to tackle this one?

I spent a lot of time trying to figure out where the problem was but honestly I couldn't find it. If you can give me a clue maybe I could tackle this!

If you set logsFolder to any other folder than not the default, does it work? I guess this option is only working through env vars.

Although the server doesn't create the folder. Winston creates it internally I believe

I thought the same thing but the question is Why if you set PARSE_SERVER_LOGS_FOLDER env var to null the folder is not created?