---
title: "Discussion on \"Laravel .env Changes Not Reflected After Deployment: Causes and a Safe Shared-Hosting Fallback\" | Hashnode"
description: "Discussion on \"Laravel .env Changes Not Reflected After Deployment: Causes and a Safe Shared-Hosting Fallback\". Why Laravel keeps stale config after deployment, the standard fix, and a safe fallback for FTP or shared hosting without exec()."
url: "https://hashnode.com/posts/laravel-env-changes-not-reflected-after-deployment-causes-and-a-safe-shared-hosting-fallback/6a8724bf12194f94137c17d0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Laravel .env Changes Not Reflected After Deployment: Causes and a Safe Shared-Hosting Fallback](https://codegenie-be.hashnode.dev/laravel-env-changes-not-reflected-after-deployment-causes-and-a-safe-shared-hosting-fallback?utm_source=hashnode&utm_medium=feed)

Why Laravel keeps stale config after deployment, the standard fix, and a safe fallback for FTP or shared hosting without exec().

Aug 20 · 5 min read · codegenie-be.hashnode.dev  
Read the article

-   [#laravel](https://hashnode.com/tag/laravel)
-   [#php](https://hashnode.com/tag/php)
-   [#devops](https://hashnode.com/tag/devops)
-   [#opensource](https://hashnode.com/tag/opensource)

## Written by

[codegenie-be](https://hashnode.com/@codegenie-be)

@codegenie-be · Harelbeke, Belgium

  
[View profile](https://hashnode.com/@codegenie-be)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
