Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. Commented Feb 13, 2015 at 6:01
  • Edited my answer. I copied some of important note from my blog. But... why someone give me (-1) ? :( Commented Feb 13, 2015 at 6:33
  • I didn't give you the downvote so I can't be sure, but I think you probably got it because this doesn't actually answer the question. The question is "What's wrong with my configuration?" and your answer says "Do this to change your configuration...". It's related, but misses the point of the question. Look at the accepted answer and see how much more to the point it is, regarding the specific question. Commented Feb 13, 2015 at 20:04
  • 2
    A step backwards in my opinion. The point of specifying an "environment" is to be able to load correct settings for that environment without having to resort to a bunch of conditionals to....wait for it.....determine what environment I'm running in. L4 was much better in this respect - I'm "local" - OK load the "local" configs. That's the only conditional I need. Commented Mar 3, 2015 at 20:27
  • "It is easy to configure Laravel 5 environment." This is why you are being downvoted. I used to be able to set everything in my repository. Now I'm supposed to manually manage a bunch of stupid .env files outside of my repository, and I'm told this is somehow easier. Commented May 23, 2015 at 4:41