3 years ago

Category: Laravel, PHP, git

Update Aug, 11: This post was well received on Reddit, so I added new anti-patterns to reflect the comments. I spotted common anti-patterns that I had to fix. This article is not about rewriting an old PHP application to , but about how to make it more maintainable and less of a hassle to work on.

Note that it is not recommended to use the package as is in production, it is better to either: Files that contained credentials can be purged from the Git history as shown here.

This is obviously incompatible with using a .env file or Composer as it is a bad idea to expose the vendor folder.