2 Comments

  • So – how did you solve the ‘different configs in different environments’ problem?

    My thinking after my own experience of designing a deployment scheme is that code that’s not owned and developed by the developer doesn’t go into the main source control repo – separation of concerns.

    With that said, I do store configs that rarely change in their own little repos and pull them in with Composer. They still don’t go into the main repo that the devs are working in.

    • The current state of it is that repository has production configuration, which is overridden in development with local config file (for WP) and server configuration (for Apache).

Comments are closed.