Support the ongoing development of Laravel.io →
Laravel
Last updated by @valentino-emirlike 2 years ago.
0

What was the error you got when you replaced it with .env.example?

0

my apologies, that was a mistake, there was no effect

0

It's gonna be hard to help you without the env file. Can you remove any sensitive value from it (or change them in a similar way) and share it?

0
APP_NAME='app name'
APP_ENV=local
APP_KEY=base64:*****=
APP_DEBUG=true
APP_URL=http://ac.localhost

MARKETING_PLAN=20220601
WP_SITE=https://wpsite.com
WPAF_PUBLICKEY=****
WPAF_TOKEN=***
WPAF_SECRET=***
TELEGRAM_BOT_NAME=***


XDEBUG_MODE=develop,debug
XDEBUG_CONFIG='client_host=ac.localhost'
XDEBUG_PORT=9003

LOG_CHANNEL=stack
LOG_DEPRECATIONS_CHANNEL=null
LOG_LEVEL=debug

DB_CONNECTION=mysql
DB_HOST=host.docker.internal
DB_PORT=3306
DB_DATABASE=laravel_dev
DB_USERNAME=emirptaa
DB_PASSWORD=password

DB_HOST_WP=mariadb
DB_PORT_WP=3306
DB_DATABASE_WP=wp-dev
DB_USERNAME_WP=root
DB_PASSWORD_WP=password


BROADCAST_DRIVER=log
CACHE_DRIVER=file
FILESYSTEM_DISK=local
QUEUE_CONNECTION=sync
SESSION_DRIVER=database
SESSION_CONNECTION=mysql
SESSION_LIFETIME=120

MEMCACHED_HOST=memcached

REDIS_HOST=redis
REDIS_PASSWORD=null
REDIS_PORT=6379

MAIL_MAILER=failover
MAIL_HOST=email-smtp.eu-central-1.amazonaws.com
MAIL_PORT=587
MAIL_USERNAME=***
MAIL_PASSWORD=***
MAIL_ENCRYPTION=tsl
MAIL_FROM_ADDRESS=noreply@***.com
MAIL_FROM_NAME=${APP_NAME}

AWS_ACCESS_KEY_ID=***
AWS_SECRET_ACCESS_KEY=***
AWS_DEFAULT_REGION=eu-central-1
AWS_BUCKET=***
AWS_USE_PATH_STYLE_ENDPOINT=false

PUSHER_APP_ID=
PUSHER_APP_KEY=
PUSHER_APP_SECRET=
PUSHER_APP_CLUSTER=mt1

VITE_PUSHER_APP_KEY=${PUSHER_APP_KEY}
VITE_PUSHER_APP_CLUSTER=${PUSHER_APP_CLUSTER}

CONTAINER_PORT=8080

Last updated 2 years ago.
0

I copied and pasted this in my env file in one of my projects and it works perfectly. No idea what's wrong on your side.

Last updated 2 years ago.
0

I worked around the issue by rolling back to a previous version of Composer

0

actually this is still a huge problem.

It occurs whenever I use schedule:run or schedule:work I think this might be the real reason behind this issue https://laravel.io/forum/schedulerun-calls-for-translation-and-causes-an-exception

PHP Warning:  Failed to set memory limit to 0 bytes (Current memory usage is 2097152 bytes) in Unknown on line 0
The environment file is invalid!
Failed to parse dotenv file. Encountered an invalid name at [APP_NAME].

What's the meaning of the first line? What's trying to set the memory limit to 0?

Last updated 2 years ago.
0

the problem doesn't appear on a Sail host. It does on my host. Can someone please help me understand what's missing? I tried to compare phpinfo() results but I can't find notable relevant differences

0

Sign in to participate in this thread!

Eventy

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.