-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use FORGE_ENV_KEYS when .env.example contains empty lines #127
Comments
@Liamso, could you try removing FORGE_ENV_KEYS from your Harbor config? If that doesn’t make it work yet, you might have an issue with the Maybe give Laravel’s default |
Thanks a ton @mehrancodes . Without the FORGE_ENV_KEYS, it does indeed work. With my Thanks for your work on this tool - it's really great. If I happen to find time in the coming days would you be open to a PR that introduces phpdotenv as the env parser which should mirror what Laravel accepts a little more closely? |
@Liamso, Could you share a snippet of your GitHub workflow where you’re seeing this error? Thanks for checking out Harbor - it’s built on Laravel Zero and uses phpdotenv for handling environment variables. |
Sure @mehrancodes;
|
Looks like it's empty lines in the .env.example which makes sense when reading
Will let you close if you want @mehrancodes - thanks again for the tool. I'll update the title & description to better reflect the issue I was experiencing. |
huh, this one's cropped up again on one of our PRs, even after removing whitespace. Will let you know if there's anything we identify causing it. |
Running harbor with the line
Results in the following:
Have attempted with multiple var options - this seems like the simplest reproduction step with just a single value in there. It doens't work with the
;
delimiter at the end, either.It appears that this issue only persists when there are empty lines in the .env.example
The text was updated successfully, but these errors were encountered: