Originally created by @Noggog on GitHub (Feb 24, 2025).
I had some trouble deploying a stack after editing back and forth on the environment variable UI controls.
One I was able to narrow down was the behavior of the Env File Path textbox. On a fresh stack, it has the actual text contents ".env". This of course makes sense as a default value.
However, when running the stack, I got the error "failed to write environment file "Path/To/Stacks" is a folder
This suggests that even though the watermark suggests it'll use .env as the file name, the logic does not and bugs out
Originally created by @Noggog on GitHub (Feb 24, 2025).
I had some trouble deploying a stack after editing back and forth on the environment variable UI controls.
One I was able to narrow down was the behavior of the `Env File Path` textbox. On a fresh stack, it has the actual text contents ".env". This of course makes sense as a default value.
However, if you remove the text ".env" so that it's an empty textbox, a "watermark" `.env` shows up in the box. This suggests that since the textbox is empty, it'll be using `.env` as the path as a fallback. Here's a video of what I mean:
https://github.com/user-attachments/assets/ae8ca7b6-9d92-4acd-ba31-1b1678ab0724
However, when running the stack, I got the error "failed to write environment file "Path/To/Stacks" is a folder

This suggests that even though the watermark suggests it'll use `.env` as the file name, the logic does not and bugs out
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Noggog on GitHub (Feb 24, 2025).
I had some trouble deploying a stack after editing back and forth on the environment variable UI controls.
One I was able to narrow down was the behavior of the
Env File Pathtextbox. On a fresh stack, it has the actual text contents ".env". This of course makes sense as a default value.However, if you remove the text ".env" so that it's an empty textbox, a "watermark"
.envshows up in the box. This suggests that since the textbox is empty, it'll be using.envas the path as a fallback. Here's a video of what I mean:https://github.com/user-attachments/assets/ae8ca7b6-9d92-4acd-ba31-1b1678ab0724
However, when running the stack, I got the error "failed to write environment file "Path/To/Stacks" is a folder

This suggests that even though the watermark suggests it'll use
.envas the file name, the logic does not and bugs out